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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds genuinely non-obvious behavior: the tool is free and requires no x402 payment challenge, plus the 100-operator eligibility gate that determines voting_locked. It omits error behavior for unknown proposal ids, so it falls short of a 5.

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 returned-field list is front-loaded and useful, but 'FREE — no payment required: call directly without payment (no x402 challenge; this tool is free)' states the same fact three times in one sentence. Tightening that redundancy would cost nothing in clarity.

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, the description correctly takes on the burden of naming the returned fields and the eligibility rule. For a one-parameter read tool that is nearly complete; only error/not-found behavior is left unstated.

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%, so the description must carry the parameter meaning, and it does: the HTTP equivalent 'proposals/{id}/vote-status' makes clear that id is a proposal identifier. That is meaningful added semantics for a single undocumented parameter.

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 (read vote status) and enumerates exactly what is returned: live eligible count, eligible_floor, and the computed voting_locked state. It does not name or contrast with the closest siblings (commons_get_tally, commons_get_proposal), so the agent must infer the boundary itself.

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 threshold rule ('No vote opens below 100 eligible verified operators') implies this is a pre-check before commons_cast_ballot, and the free/no-payment note helps selection. But there is no explicit when-to-use/when-not or a named alternative such as commons_get_tally.

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