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

With no annotations, the description carries full burden. It usefully discloses two behavioral traits: the one-vote-per-agent limit and the webhook (wish.filled) notification triggered when a seller offers the wish. However, it omits auth requirements, error behavior if already voted, and what voting actually changes.

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?

Two compact sentences, front-loaded with the core action and constraint before the notification detail. No filler, though the webhook parenthetical is somewhat tangential to the invocation itself.

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 single-parameter tool with no output schema and no annotations, the description covers the effect, the voting limit, and the async notification reasonably well. It still leaves gaps around parameter sourcing and failure modes, so it is adequate but not complete.

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 0%, so the single required wish_id is undocumented in both schema and description. The description implies the wish must be one 'you share' but gives no format, source, or validity guidance for the id, leaving a real gap for the only 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+resource combination ('Add your vote to a wish') with a clear scope constraint ('a wish you share'). It implicitly distinguishes from siblings like fill_wish and list_wishes, though it does not name them explicitly.

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 parenthetical '(one per agent)' hints at a constraint, and 'a wish you share' implies a precondition, but there is no explicit when-to-use guidance or comparison to siblings such as fill_wish or wish. The agent must infer the context.

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