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

With no annotations, the description carries the burden well: it discloses the one-vote-per-human constraint, that an agent mandate is required, and that the bearer token must be configured in the MCP client rather than passed as an argument. It does not say what happens on a duplicate vote, a closed proposal, or whether the vote is final — the remaining behavioral gaps.

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?

Three labeled lines — behavior, when to use, notes — plus a compact example. Front-loaded, zero filler, and each line carries distinct information.

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 and no annotations, so the description must supply everything; it covers auth, the vote constraint, and the prerequisite read. Missing are the return/confirmation semantics and failure modes (duplicate vote, closed proposal), which are the notable remaining gaps.

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 100%, so the baseline is 3, but the 'Example arguments' block adds concrete value by showing the id format ('is_0123456789ab') and the Italian enum value in situ. It also reinforces that proposal_id originates from list_proposals.

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 ('Record a consultative vote on an open proposal') and immediately scopes the semantics ('one vote per human guarantor, not per agent'). This distinguishes it from submit_proposal and list_proposals without needing the schema.

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?

Explicit 'When to use' sentence routes the agent through list_proposals first, which is a real ordering dependency. It does not state when-not to use it (e.g. proposal closed, already voted, no mandate), so it stops short of full alternative coverage.

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