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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds behavior annotations don't carry: results are sorted newest first, normalized to a single cross-platform format, and paginated via a cursor. It stops short of describing page-size behavior or what an empty/end-of-results response looks like.

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 short sentences, both front-loaded with the highest-value facts (ordering, uniform format) before the filter/pagination detail. Nothing is padding.

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?

With 6 optional params, no output schema, and read-only annotations, the description covers filtering, ordering, and pagination adequately; 'next_cursor' implies a cursor in the response. It leaves the limit parameter and pagination termination behavior undocumented, which is a modest gap for a paging tool.

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 67%, and the description maps its 'location, platform, date or whether they have a reply' phrasing onto location_id, platform, since, and has_reply, plus cursor handling. That's useful framing, but it adds no format or syntax detail beyond what the schema already states, and the limit parameter goes unmentioned.

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 names the resource (reviews), its ordering (newest first), and a key property (uniform format across every platform), which is more specific than the title 'List reviews'. It doesn't explicitly contrast with siblings like get_review or get_stats, but the listing/filtering scope is unmistakable.

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 tells the agent what can be filtered on and how to paginate ('Use next_cursor for the next page'), which is real usage guidance for retrieval. However, it never says when to choose this over get_review (single review) or get_stats (aggregates), so the alternatives are only implied by the sibling names.

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