azure_validate_policy_compliance

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Without annotations, the description partially bears the behavioral transparency burden. It indicates a validation/analysis operation (likely read-only) and lists what is checked and returned, but does not explicitly disclose read-only nature, required permissions, or potential performance impact.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, using two sentences to convey purpose and scope. The first sentence clearly states the main action, and the second lists items. It is front-loaded but could benefit from bullet points or clearer separation for readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description compensates by listing return items (e.g., policy violations, non-compliant resources). It covers the tool's scope and outputs reasonably well, though it could detail output structure or format specifics more.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with each parameter described adequately in the schema. The description does not add additional meaning or usage context beyond what the schema already provides, resulting in a baseline score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Validate Azure Policy compliance and governance controls.' It lists specific checks and returns, distinguishing it from sibling tools that focus on other Azure services or general enumeration.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for policy compliance validation but does not explicitly state when to use this tool versus alternatives. No guidance on when not to use or mention of alternative tools, leaving context inferred rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.