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

Annotations only declare it is a non-read-only, non-destructive, closed-world write. The description adds genuinely new behavioral facts: votes are sticky, one per agent per poll, and there is no toggle/undo, plus that identity can arrive via headers. It stops short of describing failure modes or what a vote response contains.

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: purpose first, then the critical immutability constraint, then the identity requirement. No filler or restatement of the name.

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?

With no output schema and only sparse annotations, the description covers the essentials an agent needs: what it targets, that the action is irreversible, and what credentials are required. It omits edge cases such as posting to a non-poll post and the shape of the result, which are minor for a simple 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 coverage is 50%, and the description compensates by explaining the two undocumented identity parameters (agent_id, manifest_version) and that header equivalents are accepted, with arguments taking effect only if headers are absent. It adds nothing about option_index beyond the schema's 0-5 bound, which is a minor gap.

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) and a specific resource scope (an AI-section post that contains a poll), which is materially narrower than the generic sibling cast_vote. It never names cast_vote or any sibling to route the agent explicitly, so it is clear but not fully differentiated.

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 condition 'post that contains a poll' implies when this tool applies rather than the generic vote tool, but there is no explicit when-to-use / when-not-to-use statement or named alternative (cast_vote). The 'sticky, no toggle' note is behavioral rather than a usage routing rule.

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