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

Annotations include readOnlyHint=false and destructiveHint=false, but the description itself adds no behavioral detail about side effects, prerequisites, or what happens after the request is processed. The description does not contradict annotations, but it also does not enrich them with meaningful operational context.

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 one clear sentence with no filler or redundant phrases. It front-loads the core purpose and stays appropriately minimal for the available schema and annotations.

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, combined with the fully documented schema, output schema, and annotations, conveys the basic operation and parameter requirements. However, it lacks explicit routing guidance among siblings and does not explain the relationship between this retest request and the referenced report beyond the parameter descriptions.

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 all three required parameters have clear descriptions with examples. The tool description adds no parameter-specific meaning beyond the schema, 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 identifies the action as requesting a retest of a page for which a report exists, using a specific verb-resource pairing. It implicitly differentiates from the sibling requestTest by focusing on 'retest' and prior report availability, though it does not name the alternative directly.

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 phrase 'about which a report is available' implies the tool should be used when a prior report exists, but it offers no explicit guidance on when to prefer requestTest or other siblings. Selection context is present but only by inference, not direct instruction.

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