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

Annotations already declare readOnly/idempotent/non-destructive safety, so the description focuses on operational detail: ordering ('newest first'), the exact fields returned including source and replies, and pagination via next_cursor. This adds useful context beyond the safety profile, though rate limits or result-size behavior are unmentioned.

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 tight sentences, front-loaded with the resource identity, then ordering/returned fields, then filtering/pagination. No wasted words and logical flow.

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?

No output schema exists, but the description compensates by enumerating the returned fields (rating, text, author, client, appointment, source, replies) and covering filtering and pagination. For a read-only list tool with full annotation coverage, nothing an agent needs 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?

With 100% schema coverage the schema itself documents all six parameters, so baseline 3 applies. The description reinforces the filter set (rating, source, words, unreplied) and pagination, but adds little syntax or format meaning beyond what the schema already provides.

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?

The description opens with a specific verb+resource ('Lists reviews'), names the domain ('Client reviews of the business'), and enumerates the returned fields. It clearly signals a read operation distinct from reply_to_review, but never explicitly names or contrasts a sibling tool.

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 describes the available filters and pagination, which implies usage, but gives no explicit 'use this when' guidance or comparison to alternatives such as reply_to_review. The listing use-case is inferable but not spelled out.

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