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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered. The description adds the incremental reading pattern and cursor reuse, which is useful context, and confirms 'without side effects,' consistent with the annotations. It does not disclose any additional behavioral traits beyond what annotations provide, but the cursor mechanism is a meaningful extra.

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 description is two sentences, front-loads the core purpose, and wastes no words. The critical pagination hint is placed early, and the optional parameter clarification is concise. Every sentence earns its place.

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?

The tool has four parameters, all described, and no output schema. The description covers the main behavior and the cursor reuse, which is the key operational detail. However, it does not hint at the response format (e.g., that it returns contributions with a next_after_seq), which could be helpful. Given the tool's simplicity and strong annotations, this is a minor gap, but it is not fully complete for an agent needing to parse results.

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 all parameters are documented. The description adds valuable meaning by explaining the cursor reuse pattern ('Reuse next_after_seq as after_seq'), which is not in the schema, and by noting 'since' is an ISO-8601 lower bound (though that is already in schema). This goes beyond the baseline and helps the agent construct correct calls.

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 states a specific verb ('Read') and resource ('one debate'), and the 'incrementally' phrasing signals paginated access to contributions. It does not explicitly name a sibling for differentiation, but 'one debate' implies it is about contributions within a specific debate rather than listing debates, which distinguishes it from list_debates and hot_debates. The purpose is clear but could be slightly more explicit about the resource being contributions.

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 provides concrete pagination guidance ('Reuse next_after_seq as after_seq on later calls') and clarifies the optional 'since' parameter, which helps the agent use the tool correctly. However, it does not explicitly state when to use this tool versus alternatives (e.g., list_debates for listing debates) or mention any exclusions. The guidance is about how to use, not when to choose it.

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