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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior, so the safety bar is lower. The description adds the pagination contract (follow pagination.next_offset while has_more is true), which is meaningful behavioral detail beyond the structured annotations and not present in any output schema.

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, zero waste, and the core action is front-loaded with the pagination rule following. Nothing is redundant.

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 annotations covering safety and no output schema, the description should carry more of the return-value burden. It explains pagination fields but omits page-size semantics (limit), default ordering, and how the three collections differ in returned content. Adequate but with clear gaps 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 coverage is 40%, below the 50% threshold, so the description should compensate more. It clarifies the collection dimension by naming the three returnable content types and conveys offset/pagination behavior, but leaves limit and the relationship between limit/offset unexplained. Partial compensation justifies a 3.

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 (Read/list) and resource (comments, revision proposals, revision history of a record), which clearly identifies the tool's function. It doesn't explicitly distinguish itself from siblings like read_change_history or read_vote_history, so it falls just short of 5.

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 phrase 'Read another page' implies a continuation/pagination use case, but no when-to-use versus alternatives guidance is given, and no sibling is named. An agent cannot tell from this text when to pick list_contributions over read_change_history or read_vote_history.

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