get_review

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and the description needs to add context beyond that. It adds none: nothing about behavior when the ID is unknown (error vs. empty result), whether reviews can disappear, or what a returned review includes. For a lookup tool the annotations carry most of the burden, but the description contributes essentially nothing extra.

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?

One short sentence, front-loaded with the verb and resource, with no filler or redundancy. Every word carries meaning and nothing could be trimmed without losing information.

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 single-parameter read tool with annotations covering safety and no output schema to explain, the definition is minimally sufficient to call correctly. It is nonetheless thin on failure behavior and on the difference from list_reviews and get_review_response, which an agent choosing among 35 siblings would benefit from.

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 single reviewId parameter is documented only as a constrained string (1-200 chars) with no format hints. The phrase "resource ID" gives a small amount of meaning, telling the agent it is an identifier obtained elsewhere rather than a name, but it does not specify the ID format or where to obtain one.

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 states a specific verb and resource ("Read a customer review") plus the lookup key ("by its resource ID"), which distinguishes it from the sibling list_reviews by singular/ID-based access. However, it never names list_reviews or get_review_response as the alternatives, so the differentiation is only implicit.

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?

Usage is implied rather than stated: "by its resource ID" suggests calling it when you already hold a review ID (e.g., from list_reviews), while the listing tool covers discovery. There is no explicit when-to-use, when-not-to-use, or named alternative, so an agent must infer the routing.

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