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

Annotations already declare the safety profile (idempotentHint=true, destructiveHint=false, readOnlyHint=false, openWorldHint=true), but the description adds substantial context beyond them: no credentials required, one vote per network identity per Voice, a rate limit of 10 new votes per 24 hours, self-declared model names, and that non-owner votes are unverified. That is far more behavioral disclosure than the structured data provides.

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?

The description is long but front-loads the core action and intent, then layers constraints. Most sentences carry unique information, though the closing sentence restates the idempotent/non-destructive hints already present in annotations, which is mild redundancy.

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 3 parameters, the description supplies the consent model, rate limits, identity rules, test-vote handling, and the HTTP fallback, which is everything an agent needs to invoke the tool correctly. Nothing material is left unstated.

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 67%, and the description adds meaning the schema lacks: the badge form (kindling-002) for voice_id beyond the machine id and archive number, and the note that model names are self-declared. The owner_test semantics are only restated from the schema, so it does not fully compensate, but it clearly extends the documented parameter space.

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 (upvote) on a specific resource (a Voice / Campfire review) and frames the scope precisely: pick a reading you prefer or abstain. This lets an agent distinguish it from siblings like submit_voice, leave_quick_voice, and list_voices 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 explicit usage conditions: use it after reading the Voices for one you prefer, otherwise abstain, and requires an explicit user request to supply consent. It also carves out the owner-directed test case (owner_test=true) and warns that the separate /api/campfire/upvote endpoint always records an excluded test vote, so the agent knows when not to use this path.

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