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

The annotations already disclose the key behavioral context: read-only, idempotent, and non-destructive. The description adds some useful detail about what the fetched review contains, but it doesn't explain error behavior, authorization, or domain-specific meaning of 'stable subject type'. There is no annotation contradiction.

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 efficiently states both the resource and the composition of the fetched review. Every word contributes value, and there is no redundant restatement of the tool name or 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 single-id fetcher, the description covers the resource and the expected contents of the returned review. It does not provide output structure or error semantics, but its simplicity and existing annotations make the description reasonably complete.

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?

The single parameter is an id with uuid format, and its meaning is semantically obvious from the tool name and description. While the schema has no description field, the parameter has very low ambiguity, so the added value of extra prose would be minimal.

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 resource and action: fetching a complete review, and names its major components: stable subject type, original words, and AI assessments. This distinguishes it from obvious siblings like save_assessment or get_deliberation, though it does not explicitly compare itself to those alternatives.

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 usage is implied by the verb 'Fetch' and the review-specific resource, so an agent can reasonably infer that this tool is for retrieving a review by ID. However, it gives no explicit guidance about when to choose this over the search or other sibling tools, nor any exclusions.

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