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

Beyond annotations (which already declare readOnly/openWorld=false/destructive=false), it discloses several traits the agent could not otherwise know: no credit is spent, a fixed disclaimer is attached, and the response deliberately omits source documents, personal fields and free-text excerpts. It also bounds interpretation by stating the result does not prove fraud, authenticity, intent, identity or AI generation.

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?

Three sentences, zero preamble: what it returns, what it withholds/costs, and how to interpret it. Each sentence earns its place, though the non-goal enumeration ('fraud, authenticity, intent, identity or AI generation') is slightly long for its informational payload.

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?

With an output schema present, return-value structure need not be spelled out, and annotations already cover the safety profile. The description adds the remaining essentials for a fraud-adjacent read tool: cost, data minimization, and explicit interpretation limits, so nothing an agent needs to call it correctly is missing.

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 coverage is 0%, so the description must carry the load, and it only partially does: it clarifies that the ID must reference a single recoverable review tied to the connected purchase, which scopes the value. It adds nothing about the required ent_<hex32> format or where the ID is obtained, leaving the regex pattern in the schema to do that work.

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?

States a specific verb (Returns) plus the exact resource (categorical status, priority, confidence, fraud/AI assessments, indicator and limitation counts) for one recoverable review from the connected purchase. The singular 'one ... review' scoping implicitly separates it from the sibling list_recent_reviews, and the 'from the connected purchase' constraint separates it from a free-standing review lookup.

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 gives decision-relevant context (it consumes no credit, and output is a signal for human follow-up rather than proof), which helps an agent judge whether to call it. However, it never states when to prefer it over list_recent_reviews or get_connected_purchase, nor prerequisites such as where a valid review_id comes from. Usage is implied rather than prescribed.

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