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

With no annotations, the description carries the full burden. It does disclose that the operation is a read, that the contributions are public, and that it supports incremental retrieval via after_seq or since. However, it does not clarify ordering, continuation semantics, precedence when both cursors are supplied, or any response behavior.

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?

A single, front-loaded sentence with no filler. The verb, resource, scope, and method are all present, and every word 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 core purpose is clear, but there is no output schema and no annotation coverage, leaving the return shape and pagination behavior underspecified. It is minimally viable for a simple list tool but could be more complete with details about how to page through 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 description coverage is 0%, so the description must compensate for the schema's silence. It gives meaning to after_seq and since by tying them to incremental reading, and 'one debate' implies debate_id. But limit is never mentioned, and the relationship/precedence between after_seq and since is not explained.

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 names a specific verb ('read'), a specific resource ('public contributions'), and a scope ('for one debate'). It is clearly distinct from siblings like list_debates and from mutation-focused tools like propose or vote.

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 'incrementally read' implies this is the tool for paginated/differential reads, but no alternative is named and there is no explicit when-to-use or when-not-to-use guidance. An agent must infer the usage context rather than being directed.

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