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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable context beyond annotations: no authentication required, the case is versioned, and the returned content includes candidate, boundary, and test prompts. No contradiction with annotations.

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?

A single, tightly written sentence with no filler. The authentication fact is front-loaded, and every remaining word contributes to specifying the operation and expected content.

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 one-parameter read tool, the description covers auth, operation, and payload composition. However, 'versioned' is ambiguous—whether it returns one version or a versioned document—and slug semantics are absent. Since there is no output schema, these gaps leave some uncertainty.

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 description coverage is 0%, and the only parameter, slug, is not explained in the description. The description does not state that slug identifies the case or how versioning affects the parameter, so it fails to compensate for the schema's lack of documentation.

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?

States a specific verb ('Read'), a precise resource ('one versioned synthetic case'), and the payload contents ('candidate, boundary and test prompts'). The singular focus clearly distinguishes it from sibling list tools like list_public_cases.

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?

Provides useful context that no authentication is needed and that this retrieves a single case, but it never explicitly explains when to choose this over list_public_cases or list_public_feedback. The usage is implied by the singular/plural contrast rather than stated.

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