azure_scan_acr_security

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

With empty annotations, the description bears full burden for behavioral disclosure. It lists checks (read-like operations) but does not mention side effects, permissions, rate limits, or whether it modifies state. The 'Checks' phrasing implies read-only, but this is not explicit.

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, consisting of one sentence followed by a focused list. It front-loads the primary purpose and then details checks. Minor formatting improvements (e.g., bullet list) could enhance readability, but overall it is efficient.

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?

The description covers many security checks but lacks explanation of output format, error handling, or prerequisites (e.g., required permissions). Given the complexity (5 parameters, no output schema), more detail on what the scan produces would be helpful.

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%, so the input schema already describes all parameters. The tool description adds no further detail about parameter usage or semantics beyond the schema, meeting the baseline but not exceeding it.

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 as a 'Comprehensive Azure Container Registry (ACR) security scanner' and enumerates specific checks (admin user, public access, vulnerability scanning, etc.), making it highly specific to ACR security. The name and description together differentiate it from sibling tools that target other Azure resources like CDN or container apps.

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?

No explicit guidance is given on when to use this tool versus alternatives such as azure_analyze_storage_security or azure_scan_all_locations. The description implies usage for ACR security scanning, but lacks context on prerequisites or exclusions.

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