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

Annotations already declare non-read-only, non-destructive, idempotent behavior, but the description adds concrete value beyond them: the required auth scope (community:vote) and the idempotency-key discipline ('Preserve request_id and payload on retries'). These are actionable details the annotations do not convey.

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?

Four short, front-loaded sentences with no filler; the core operation leads and constraints follow. 'Account and affiliation rules apply' is the only slightly vague phrase, but overall it is efficiently 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 mutation with no output schema, the description covers auth, idempotency, and value semantics, which is most of what an agent needs. It omits error behavior and whether an existing vote is overwritten, which are meaningful gaps for a state-changing vote tool.

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 0%, so the description must carry parameter meaning. It clarifies the value domain and explains request_id's retry role, but entry_id (the target of the vote) is never described, leaving one of three parameters undocumented.

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 ('Set the current account vote') plus the exact value domain (1 or -1), so the operation is unambiguous. It does not explicitly name the sibling retract_vote to contrast with, so sibling differentiation is left to inference rather than stated.

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?

Provides prerequisites ('Requires the connected identity and community:vote' and 'Account and affiliation rules apply'), which is real usage context. However, it never says when to use this versus retract_vote or the other vote-adjacent siblings, so the when/when-not guidance is only implied.

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