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

Annotations already declare this is a non-readonly, non-destructive, non-idempotent mutation. The description does not add meaningful behavioral context beyond 'cast', such as whether a vote can be changed, what happens on a repeat vote given idempotentHint=false, or what constitutes the 'VOTE window'. With annotations present, the bar is lower, but the description still adds little.

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 compact and front-loads the WHEN condition and alternative. The opening repetition of the tool name is slight waste, but overall it is appropriately sized.

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 simple mutation with full schema coverage and an output schema, the description covers purpose and sibling routing. However, it omits relevant behavioral context about vote mutation semantics and the voting window, leaving an agent with only the minimum needed to invoke it.

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 description coverage is 100%, so the schema already documents proposal_id, choice, and key. The description adds a concrete example using proposal_id and choice, but does not explain the key/auth parameter or add meaning beyond the 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 gives a specific action ('cast yes/no') and resource ('VOTE window'), and explicitly distinguishes it from syndicate_debate. It is not a tautology, though the leading 'syndicate_vote.' repeats the tool name without adding information.

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 states the triggering condition ('WHEN: cast yes/no in the VOTE window') and names the alternative sibling syndicate_debate with the differentiator 'text only'. It lacks broader when-not guidance involving other vote/ballot tools, but the core routing guidance is clear.

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