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

Annotations already declare readOnly/destructive/openWorld, so the safety profile is covered. The description adds real value beyond them: newest-first ordering and the auth requirement (Cotlet API key with app access), which an agent needs before calling.

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?

The opening sentence ('Reviews on your profile with rating, text, date and your response if any.') is largely restated by the following sentence ('Lists reviews on your pro profile... with rating, text and your response'), creating redundancy. The routing and auth details earn their place, but the lead is wasteful.

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, paginated list tool with no output schema and covered annotations, the description supplies the needed pieces: what is returned, ordering, the unanswered filter's purpose, the auth requirement, and the follow-up tool. Pagination mechanics are left to the schema, which is acceptable.

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 limit, cursor and unanswered_only are already documented in the schema; the description's restatement of unanswered_only adds no syntax or format detail beyond it. It mentions review_id, but that is a parameter of the sibling reply_to_review, not this tool, so it does not enrich this tool's own params.

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 (lists) and resource (reviews on your pro profile) and names the return fields (rating, text, date, your response). It also names the ordering (newest first) and distinguishes itself from the sibling reply_to_review, which it references explicitly.

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 conditional guidance ('Set unanswered_only to see the reviews that still need a reply') and points to reply_to_review as the companion write tool via review_id. It clearly frames the context but does not enumerate when to prefer this over other list-style siblings.

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