vote_on_service

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

Discloses key behaviors: cost (1 sat per vote, multiple votes allowed), return format (JSON with success, slug, newVoteCount), and prioritization mechanism (highest-voted services prioritized). No annotations provided, but description covers essential aspects.

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 sentences, each adding essential information: purpose, return format, cost, prerequisite, and prioritization. No wasted words, front-loaded.

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?

All necessary context is present: prerequisite tool, payment requirement, cost details, return fields, and voting impact. No output schema needed as return is described.

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 description adds value by clarifying paymentId cost and slug source, plus return structure. Extra context beyond schema justifies above baseline.

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 clearly states the action ('Vote for a planned service') and the resource ('planned service'), distinguishing it from sibling tools like list_planned_services.

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?

Explicitly instructs to call list_planned_services first and to create a payment with toolName='vote_on_service', providing clear prerequisites and workflow context.

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