Get Review

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

With no annotations provided, the description carries the burden of behavioral disclosure. The verb 'Get' signals a non-mutating lookup and 'single' indicates exactly one result, but no detail is given about error behavior, permissions, or language translation effects. It is adequate but minimal for a simple getter.

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 short sentence with no filler. 'Get a single user review by its ID' front-loads the action, resource, and scope, making it easy to parse and act on.

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 three-parameter getter with full schema coverage and an output schema, the description is nearly sufficient. It lacks a brief note on when translation_language matters or that review IDs are obtained from get_reviews, but the input schema fills those gaps and the complexity is low.

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 100%, so the baseline is 3 even though the description adds no param-level detail. The description's 'by its ID' reinforces the role of review_id, but the schema already documents review_id, package_name, and translation_language sufficiently.

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 uses a specific verb and resource: 'Get a single user review by its ID.' It clearly distinguishes this from the sibling get_reviews by emphasizing 'single' and 'by its ID.' An agent can immediately tell this is the singular lookup counterpart to the plural listing 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?

The description implies usage when a review ID is already known, but it does not explicitly state when to use this tool versus get_reviews or reply_to_review. The schema notes 'Review ID (from get_reviews)', which helps, but the description itself provides no direct guidance or exclusions.

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