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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds that the tool spans two distinct release types, but says nothing about behavior on an unknown or mismatched id, or how the two id inputs interact if both are passed.

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?

Two short sentences, both of which carry information, with the resource scope front-loaded before the argument routing. There is no filler or restatement of the title.

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 read-only detail tool with a fully documented schema, an output schema, and complete annotations, this covers what an agent needs to pick the right id. The remaining gap is edge-case behavior (both ids, neither id, invalid id), which is minor but not trivial given no required parameters.

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 baseline is 3, but the description adds meaning the schema does not: it expresses the intended alternation between deployment_id and experiment_id, which the schema merely presents as two independent nullable fields. It still does not explain precedence when both are provided.

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 names a specific resource and scope: 'Detailed view of a single blue-green deployment or experiment.' It clearly distinguishes the two modes it serves, though it never names a sibling tool (list_site_releases, list_site_deployments) as the contrast case.

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?

It gives routing guidance for the two id parameters ('Pass deployment_id for blue-green, experiment_id for an experiment'), which is the main selection ambiguity. It does not say when to use this versus list_site_releases or list_site_deployments, and with zero required parameters it never states what happens if neither id is supplied.

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