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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds substantive behavior beyond them: a hard cap of ten results, a 24-hour recovery window, most-recent-first ordering, and the fact that calling it is free (no credit spent). This is real operational context rather than a restatement of the annotations.

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?

Two tightly written sentences with zero filler: the scoping constraints (ten max, connected purchase, 24-hour window, ordering) come first, and the negative clarification about not starting a review or spending a credit lands last. Every clause earns its place.

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 zero-parameter read tool with an output schema, the description carries what the agent needs and need not explain return values. The only soft spot is that 'the connected purchase' is referenced without definition, though the sibling get_connected_purchase implies how that context is established.

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 tool takes zero parameters, which sets the baseline at 4; there is nothing to document and the description correctly makes no parameter claims. Schema description coverage is reported at 100% and the empty object schema is unambiguous.

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?

Specific verb (lists) plus a precisely scoped resource (review IDs of up to ten completed Deep Reviews from the connected purchase), including the 24-hour recovery window and most-recent-first ordering. It does not name the sibling tools (get_connected_purchase, get_review_summary), so it falls short of explicit sibling differentiation, but the negative clause 'Does not start a review or spend a credit' fences off adjacent actions.

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?

Clear context for use: only reviews still inside the 24-hour post-completion recovery period are returned, and the description explicitly rules out starting a review or spending a credit. It stops short of naming what to call instead (e.g., get_review_summary) for reviews outside that window, so no explicit alternative is offered.

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