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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds real context beyond them: the data is hash-chained and independently recountable, duplicates are surfaced rather than silently dropped, and there is no x402 payment challenge. It omits return shape/pagination, but the honest disclosure of what is included is valuable.

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?

Front-loaded with the useful content, but the payment sentence is redundant — "FREE — no payment required: call directly without payment (no x402 challenge; this tool is free)" says the same thing four times.

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?

No output schema exists, so the description must explain returns; it does by naming the three data components (tally log, recount, rejected ballots). The only gap is the unexplained id parameter semantics.

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?

With one parameter at 0% schema description coverage, the description must carry the load; it partially does by implying via the HTTP equivalent that {id} identifies the proposal. It never states the id format (address, hash, slug) or that it must reference an existing proposal.

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 and resource set: reads a hash-chained tally log, an independent server recount, and rejected/duplicate ballots. It is clearly the audit-detail endpoint versus siblings like commons_get_aggregates or commons_get_proposal, though it never names those siblings to make the contrast explicit.

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?

It implies usage ("Anyone can recount from this data") and tells the caller payment handling is unnecessary, but it never states when to choose this over commons_get_proposal or commons_get_aggregates, nor any prerequisites such as needing a valid proposal id.

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