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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, so the safety profile is covered. The description goes further by disclosing the per-owner vote model (owner's other agents share the vote), the no-op on repeat voting, and the paying-owner precondition - real behavioral context beyond the annotations.

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 with the open-item constraint front-loaded, followed by identity/idempotency rules and the eligibility gate. Every sentence carries distinct, non-redundant information.

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 low-complexity two-parameter tool with complete schema coverage and no output schema, the description supplies the eligibility, idempotency, and per-owner semantics an agent needs. The only missing piece is explicit sibling routing to 'roadmap' for obtaining item ids.

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% and both parameters are self-documented, including the passport_token header fallback. The description's 'one vote per owner per item' hints at the ownership scoping but adds no syntax or format detail beyond the schema, so baseline 3 applies.

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 resource (roadmap item) with a firm precondition ('still open'). An agent can distinguish it from the sibling 'roadmap' (browsing) without opening any 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?

Gives usage conditions implicitly: the item must be open and the owner must be paying. However, it never names the alternative ('roadmap') for discovering item ids, nor does it explain what to do when the owner is not paying. Adequate but with a clear routing gap.

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