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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely new behavioral facts: results are capped at 40, review text is truncated to the first 500 characters, and the returned fields are enumerated. It doesn't state what happens beyond the 40 cap (pagination or ordering), which keeps it below a 5.

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?

Front-loads what is listed and where from, then filters, then next-step routing. Every clause carries information — field list, cap, truncation, filters, sibling handoffs — with no filler or repetition of the title.

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 list tool with no output schema, the description supplies the return shape, the 40-item limit, and text truncation, which is most of what an agent needs. Ordering and what happens past the cap are unstated, leaving 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 coverage is 100%, so the baseline is 3, but the description adds interpretive meaning: the star-filter rationale ('the ones to handle first') and the note that id from the results feeds reply_to_review. That goes beyond the bare schema text for maxRating/minRating.

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?

Specific verb+resource ('List reviews') with scope (Google Business Profile and other networks) and a hard cap of 40. It explicitly distinguishes itself from the sibling list_booking_reviews, which handles Ignix booking-page reviews separately.

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 concrete when-to-use guidance: filter with minRating/maxRating, with a worked example ('maxRating 3 for the ones to handle first'). It also routes the agent to reply_to_review for answering and to list_booking_reviews for the separate review source, so alternatives are named, not implied.

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