reviews_get

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Get' implies a read-only operation, but the description does not explain the behavior of the 'include' parameter, potential errors, or any access requirements, leaving ambiguity beyond the basic fetch action.

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, front-loaded sentence with no redundant filler. It states the verb and object directly, making it easy to parse quickly.

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?

Although an output schema exists and the tool is relatively simple, the description omits crucial context about the 'include' parameter and any usage distinctions from sibling tools. This makes the description incomplete for an agent that needs to correctly invoke the tool with meaningful options.

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%, so the description must compensate for parameter meaning. The phrase 'a specific customer review' implicitly refers to review_id, but the 'include' parameter is completely unexplained, and its default null behavior is unclear without additional context.

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 the specific verb 'Get' and identifies the resource as 'a specific customer review,' which clearly distinguishes this single-item retrieval tool from sibling tools like reviews_list and reviews_search. It does not explicitly mention the review_id parameter by name, but 'specific' implies lookup by identifier.

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?

No guidance is provided on when to use this tool versus alternatives such as reviews_list or reviews_search. There is no mention of suitable scenarios, prerequisites, or exclusions, so an agent receives no help in choosing among the review-related siblings.

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