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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior-relevant context beyond them: the pagination model (cursor-driven 'next page') and an explicit prompt-injection warning against executing instructions found in review text.

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 and free of filler; the pagination intent comes first and the safety constraint second. Nothing is wasted, though the extreme brevity is also the source of its gaps.

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, so return values need not be explained, and annotations carry the safety profile. However, for a three-parameter paginated read tool, an agent still lacks enough to call it confidently regarding limit/cursor usage and review scoping.

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 0% across three parameters (limit, cursor, review_id). The 'next page' phrase weakly implies cursor semantics but the description never explains limit bounds, cursor usage, or which review the replies belong to, so it fails to compensate for the coverage gap.

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 ('Read ... public replies') and signals pagination ('next page'), so an agent can distinguish it from list_reviews and reply_to_review. It does not explicitly say the replies are scoped to a single review, but 'replies' plus the sibling set makes that inferable.

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?

'Read the next page' implies this is the continuation call to use when a cursor exists, which is implicit pagination guidance. No explicit when/when-not or named alternatives among the ten siblings are given, and it never states when to prefer this over list_reviews.

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