get_review

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

With no annotations, the description must carry the full burden of transmitting behavioral details. It discloses what the return includes (the full comment thread), which is useful, but it does not mention whether this is a read-only operation, any authorization needs, or potential errors. This is acceptable for a simple getter but leaves gaps.

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 exactly two sentences, front-loaded with the primary action and then the return contents. It wastes no words and includes a critical workflow hint without redundancy.

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 getter tool with full schema coverage and no nested objects, the description provides all essential context: what it returns, how to identify the review, and where to obtain the ID. Lacking an explicit statement about being read-only is a minor omission, but the verb 'get' and the informative return description make it sufficiently 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 input schema provides 100% description coverage for all three parameters, including 'Review ID as returned by list_reviews' for review_id. The tool description repeats this source but does not add new parameter-level 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 states the tool 'Get a single user review by its reviewId' and specifies the return includes 'the full comment thread (user comment and any developer reply)'. It also distinguishes from sibling tools by noting review IDs come from list_reviews, making it unambiguous as a single-item retrieval tool.

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 provides contextual guidance by explicitly stating 'Get review IDs from list_reviews', which tells the agent where to obtain input for this tool. It implies use when you need a specific review, but it does not explicitly discuss exclusions or when not to use it, so it earns a 4 rather than a 5.

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