Address review comment in Add CI test to validate Azure MCP tool names

[kvenkatrajan]

Issue to address comment in Add CI test to validate Azure MCP tool names in skill markdown files

Address review comment - #1709 (comment)

Greedy match is fine today because every azure__ in current skills is bounded by backticks or whitespace - I grepped. But if a skill ever writes the MCP function-call form azure__storage_blob_list as a single token, this will fail: greedy capture grabs storage_blob_list, which isn't in the snapshot (only storage is).
Two low-cost options if you want to harden it:
After extracting the suffix, try progressively shorter prefixes down to the first underscore before declaring invalid.
Leave it strict and document the convention in the snapshot header so authors know compound forms aren't supported.

[github-actions]

Thanks for opening this issue, @kvenkatrajan! 🙌

This issue tracks a code hardening improvement to the CI test that validates Azure MCP tool names — specifically making the greedy suffix matching more robust against compound tool-name forms like azure__storage_blob_list. It's been labeled as an enhancement under skills and integration-test since it improves existing test infrastructure. A coding agent (assign-to-copilot) has been assigned to look into implementing one of the two proposed hardening approaches from the PR review comment.

Generated by Issue Triage for issue #1946 · ● 121.9K · ◷