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

With no annotations, the description must carry the behavioral load: it does disclose the auth requirement ('Requires user token') and what each verdict means, which is useful. It omits what the vote actually does (does it change lead status, affect scoring, notify anyone), whether it is idempotent or reversible, and whether one vote per user per lead is enforced.

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?

Front-loaded with the action, followed by a compact taxonomy and a one-clause prerequisite. No filler sentences, no restatement of the tool name.

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 3-parameter mutation tool with no output schema and no annotations, the description covers purpose, verdict selection, and auth. It leaves notable gaps: the result of a successful vote and the effect on the lead's state are unexplained, which matters for a write operation.

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%, so the baseline is 3, but the description adds real meaning beyond the bare enum by defining the boundary between 'junk' and 'closed' and spelling out what qualifies as 'scam'. The optional 'reason' parameter is left to the schema, which is acceptable given full coverage.

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?

Names a specific verb+resource ('Cast a verification or quality vote on a lead') and enumerates the four verdict categories, which cleanly separates it from siblings like submit_lead or search_leads. It stops short of explicitly naming an alternative tool, but the action is unambiguous.

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 glosses (junk = spam/course/ad/not work, scam = fraud/upfront fee/illegal, closed = expired/taken) genuinely help pick between verdicts, and 'Requires user token' states a precondition. However, there is no guidance on when to vote at all versus inspecting the lead first, no mention of re-voting or changing a prior vote, and no explicit sibling routing.

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