arm_get_deployment_test_coverage

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

The description includes 'GET' and 'Retrieves', implying a read-only operation. However, with no annotations, it does not explicitly state side-effect-freedom, authentication needs, or response behavior. It adds minimal context beyond the name and endpoint.

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 that directly states the HTTP method, endpoint, and purpose. Every element adds value with no redundant wording.

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?

For a simple GET retrieval with fully described parameters, the description adequately conveys the tool's purpose and return type at a high level. Although no output schema exists, the phrase 'Apex test and code coverage details' gives sufficient orientation for an agent to select and invoke the 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%, with both required parameters fully described in the schema. The description's endpoint template ({label}, {iterationNumber}) adds no new meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 resource (Apex test and code coverage details) and the action (Retrieves) for a deployment iteration. The endpoint template further specifies the resource. It is distinct from sibling tools like arm_get_deployment_components, which focus on other aspects.

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 when needing test coverage details for a deployment iteration. While it doesn't explicitly name alternatives or exclusions, the specialized purpose is clear enough to guide tool selection among the sibling getters.

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