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

Beyond the safety annotations, it discloses access requirements ("Public; no OAuth required"), scope limits (only moderated, published reviews; no pending reviews), and result interpretation ("an empty list means no published reviews, not a zero-star rating"). These are exactly the behavioral facts an agent needs that annotations alone do not provide.

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?

Four tight sentences, each carrying distinct information (scope, return content, pagination rule, auth), with the resource statement front-loaded. No filler or repetition.

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 read-only, filterable list tool with an output schema present, the description covers scope, return contents, pagination constraints, auth requirements, and empty-result semantics. 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 100% so the schema already documents each parameter, but the description adds interpretive value by stating page/cursor mutual exclusion and, more usefully, that an empty result reflects no published reviews rather than a missing rating. That goes slightly beyond the raw field docs.

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 and resource ("Read customer feedback for a product") and explicitly contrasts it with the sibling get_product by denying the specification use case. An agent can immediately tell this fetches reviews, not product details.

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?

Tells the agent the product must first be obtained via get_product and gives concrete invocation rules ("Use page or cursor, never both"). It clarifies when-not (no specifications, no review submission) but stops short of naming other review-related alternatives, of which there appear to be none.

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