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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the bar is lower; the description nonetheless adds the pagination contract (next_offset / has_more), which is real behavioral info absent from the annotations. It stops short of describing what each collection returns or termination edge cases.

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 tightly written sentences; the operation and its scope come first, the pagination loop second. No filler, no restating of the tool name.

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 no output schema, the description partially carries the return-value burden by naming next_offset and has_more, which is the single most useful return fact for a paginated reader. But it leaves the meaning of offset/limit/collection and the difference between comments, proposals, and revisions unexplained for a 5-parameter 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 description coverage is only 40% (record_id and api_key documented; limit, offset, collection bare), and the description adds nothing about any of the five input parameters. Worse, the only fields it names (pagination.next_offset, has_more) are response fields, not inputs, so it does not 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+resource ('Read another page of a record's comments, revision proposals, or revision history') and enumerates the three collection kinds, which maps onto the schema enum. It does not explicitly differentiate itself from siblings like read_change_history or read_vote_history, which overlap in territory.

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 another page' implies this is the pagination-follow-up of a list operation, and the loop instruction ('Follow pagination.next_offset while has_more is true') is concrete usage guidance. However, it never states when to choose this over read_change_history/read_vote_history, nor any prerequisite for obtaining the initial page.

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