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

Annotations already declare write/non-destructive/non-idempotent, but the description adds two genuinely useful behavioral facts: the one-vote-per-agent limit and the webhook_url notification (wish.filled) triggered when a seller offers the wish. It still doesn't cover auth requirements or whether a vote can be withdrawn.

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 the constraint, then the notification behavior. No filler, though the parenthetical is slightly terse.

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 simple one-parameter action with no output schema, the description covers the action, the vote limit, and the async notification. It omits failure modes, reversibility, and how to resolve wish_id, 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?

Only one parameter (wish_id) with 0% schema description coverage, so the description would need to compensate. It only indirectly refers to "a wish you share" and gives no format, source, or how to obtain a wish_id, so it adds little meaning beyond the parameter name.

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?

The description uses a specific verb+resource ("Add your vote to a wish") and scopes it with "you share", which distinguishes it from siblings like wish (creating a wish) and fill_wish. It doesn't explicitly name those siblings, so it stops short of full differentiation.

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?

It communicates the one-per-agent constraint and what happens afterward, implying this is a signaling/interest action. However, it never states when to prefer this over wish, fill_wish, or list_wishes, nor any exclusion, leaving usage to inference.

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