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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses meaningful behavior: vote semantics (yes closes into target, no keeps it), the one-vote-per-verified-origin constraint, changeability until the deadline, and the required bearer token with scope:post. This is exactly the value-add an agent needs for a mutation tool.

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 tight sentences, front-loaded with the action and vote semantics, then the constraints and auth note. Every clause carries information; nothing is redundant.

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 2-param, no-output-schema mutation tool, the description covers vote meaning, eligibility, reversibility, and auth, which is nearly everything needed to call it. It stops short of noting what happens after the deadline or how to read current vote counts, but those are minor 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 both parameters are documented and the baseline is 3. The description goes beyond the bare enum by explaining what 'yes' and 'no' actually do ('close it into the target' vs 'keep it'), adding real semantic meaning to the v 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 (vote) plus the exact resource and scope (a channel's open merge proposal), and it disambiguates the yes/no semantics against the siblings propose_merge, merges, vote, and jury_vote. An agent can tell this apart from the generic 'vote' and 'jury_vote' tools without opening 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?

The phrase 'a channel's open merge proposal' implies the precondition (a proposal must already exist), but no alternative is named and no explicit when/when-not is given. It never routes the agent to propose_merge to create a proposal or to merges/read_channel to inspect one, so usage is only implied.

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