azure_analyze_app_service_security

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

With no annotations, the description must disclose behavioral traits. It lists what it checks but does not clarify if it is read-only, required permissions, or if it produces a report. The word 'analysis' is vague.

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 a single sentence with no wasted words, but the list of checks could be structured (e.g., bullets) for readability. Still 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?

Missing output schema and annotations; the description only lists aspects checked but does not explain what the tool returns or its behavioral impact. Lacks completeness for a security analysis tool.

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% and description adds no extra meaning beyond schema for the three parameters (subscriptionId, resourceGroup, format). Baseline score applies.

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 tool name and description clearly state it analyzes security of App Service, listing specific security aspects (HTTPS-only, TLS, authentication, etc.). This distinguishes it from sibling tools focused on other Azure resources.

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 use for App Service security analysis but does not explicitly state when to use this tool versus alternatives, nor does it provide exclusions or usage context (e.g., when to prefer it over other analysis tools).

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