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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavior: default sort order (newest first) and the nuanced definition of 'needs_attention' as pending, rejected, or delisted by Google. It stops short of describing pagination behavior or how the rating stats are aggregated.

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 dense sentences with zero filler: the core operation and ordering come first, the filter modes second, the side-payload last. Every clause carries information an agent would otherwise have to infer.

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 5-parameter read tool with no output schema and thin schema coverage, the description covers purpose, ordering, filter semantics, and the bonus return of overall rating stats. What is missing is pagination guidance (offset/limit interplay) and a hint at the shape of a returned review, which leaves a small gap.

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 only 20% (just limit), so the description has to carry the weight and largely does: it defines all three `filter` enum values semantically and explains that filtering can also happen 'by star rating'. The `offset` and `profile_id` parameters remain unexplained in both places.

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 ('List Google reviews for a profile') plus the ordering ('newest first') and the payload ('with reply status'). No sibling tool lists reviews, so the scope alone is enough to separate it from draft_review_reply and request_review_reply.

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?

The description explains what each filter mode selects ('unanswered', 'reviews needing attention (reply pending, rejected or no longer shown by Google)'), which implies when to pick each. However, it never says when to use this tool versus the reply-oriented siblings, and gives no explicit exclusions or prerequisites.

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