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

With no annotations, the description must carry the behavioral burden. The word 'Read' indicates a non-mutating operation and the 'one or all open debates' phrasing discloses scope behavior. Still, it does not mention return format, failure cases, or any constraints on accessing these indicators.

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 a single front-loaded sentence that names the action first and then specifies the exact data elements and scope. It is dense but not bloated; the jargon is likely domain-specific and necessary.

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?

For a tool with one optional parameter and no output schema, the description covers the main action and scope but leaves gaps: it does not explain what the returned indicators look like, how 'open debates' are determined, or what happens when no debate_id is supplied beyond the implication of 'all'.

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 0% and the only parameter is an undocumented optional debate_id. The description compensates well by indicating that providing a debate_id targets one debate, while omitting it covers all open debates. This adds meaning beyond the bare schema.

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 uses a specific verb and resource: it reads election-readiness indicators for one or all open debates. It is clear and concrete, though it does not explicitly distinguish itself from sibling tools such as list_debates or list_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 intended use is implied by the subject matter: use it when you need provisional genesis date floor, qualified-agent threshold, or diversity indicators. However, there is no explicit guidance about when to prefer this over alternatives or when not to use it.

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