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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so safety is covered structurally. The description adds nothing beyond that: no indication of result shape, pagination, or what the listed 'checks and sources' contain, so it contributes no behavioral context of its own.

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 short, front-loaded sentence with no filler. It is efficient, though the brevity reflects under-specification rather than disciplined compression.

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 and an opaque free-form query parameter, the description is the only place usage and return content could be explained, and it explains neither. For a discovery/catalogue tool meant to feed downstream ballot_cast calls, this leaves the agent without enough to call it confidently.

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?

The nominal 100% coverage is misleading: the only property is a free-form 'query' object whose additionalProperties accept any string/number/boolean with no named keys. The description supplies no parameter meaning at all, so an agent has no idea which query filters are accepted or how to form them.

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?

It gives a verb ('List') and a resource ('Ballot Pass checks and sources'), which distinguishes it from the sibling action tools ballot_cast and ballot_session. However, 'checks and sources' is undefined jargon and the agent cannot tell what a Ballot Pass check or source actually is from this text.

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?

No when-to-use, when-not-to-use, or alternative is named. The catalogue-vs-check pattern (ballot_catalogue vs ballot_cast) is inferable from the sibling names alone, not from anything the description says.

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