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

Annotations already declare idempotentHint=true, destructiveHint=true, and readOnlyHint=false. The description adds useful behavioral context by noting that prior attributed votes are preserved and that the tool does not attest reads or grant permission, but it does not elaborate on what destructive behavior occurs or how retries interact with vote history.

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 core action before adding constraints. The final sentence about not attesting reads or granting permission is slightly cryptic but still short and likely relevant to the tool's security model.

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 destructive, idempotent mutation with six required parameters and no output schema, the description covers some important behavior (vote preservation, reason length, permission limits) but leaves critical gaps around base_revision semantics and what happens to an existing vote when changed.

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 67%, and the description mentions base_revision and the 160-character reason limit but does not explain what base_revision represents (e.g., poll revision for concurrency control) or what option_id/poll_id/client_id/room_id mean beyond the schema. The schema descriptions for poll_id, client_id, and option_id are generic and nearly identical, so the description does not compensate for the remaining semantic gaps.

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 states a specific verb and resource: 'Records a participant's current option preference' tied to a poll vote. It clearly distinguishes casting/changing a vote from listing polls or proposing poll results, but it does not explicitly name sibling alternatives, so it falls short of the top score.

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 title 'Vote or change your vote' implies the basic use case, but the description gives no explicit when-to-use guidance, no prerequisites, and no alternatives. An agent must infer from context whether to call vote_poll versus weigh_in, open_decision, or propose_poll_result.

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