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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond that: it is free, requires no API key, and discloses what the response contains (average, distribution, team replies). It says nothing about pagination limits or whether results are cached/fresh, which keeps it at a 3.

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 sentences, front-loaded with the resource and payload, then the selection rule and the free/no-key fact. No filler and nothing redundant.

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 listing tool with full annotation coverage and no output schema, the description carries the right load by describing the returned fields. The remaining gap is pagination behavior — how to page through more than one batch and what the default ordering yields — which an agent would otherwise have to guess.

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 50%, and the description adds no parameter-level detail at all. However, the two undocumented parameters (limit, offset) are conventional pagination fields, while the non-obvious ones (sort enum, rating filter) are described in the schema, so the practical gap is modest.

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+resource (list published reviews of Geocode AI) and enumerates the payload: average rating, distribution, and team responses. The phrase 'what other users think' implicitly separates it from get_my_review and submit_review, though neither sibling is named outright.

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?

Gives an explicit trigger condition ('Use it when the human asks what other users think'), which is clear usage context. It stops short of naming the alternative for reading one's own review or for writing a review, so routing among the three review tools still requires inference.

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