Vote for the Next Drop (Crowd Control)

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

With no annotations provided, the description carries the full burden of disclosing behavior. It reveals a key non-obvious behavior: when no token is passed, the tool does not error but returns an authorization link for the user to click. It also mentions environment variable support. It does not describe the success response shape, but the most important behavioral edge case is covered.

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 four sentences and front-loads the core purpose. The token explanation is a bit verbose ('NO TOKEN IS NOT AN ERROR' in caps) but each sentence provides necessary information. It is concise enough for an API description and does not waste words.

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?

Given the tool's moderate complexity (3 params, one optional, auth flow) and no annotations or output schema, the description covers the essential context: prerequisites (get_crowd_control), parameter sourcing, token behaviors, and the no-token fallback. It doesn't describe the success response, but that is partially inferable. The description is sufficiently complete for an agent to use the tool correctly.

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 description coverage is 100%, so the baseline is 3. The description adds meaningful context beyond the schema: it explains that token is a PAT tied to the human's account, can be provided via environment variable, and omitting it triggers the auth link flow. It also reinforces that trackId comes from get_crowd_control. This adds value over the bare schema descriptions.

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 tool's purpose: 'Cast your human's vote for which candidate drops next on a channel (KBK Crowd Control).' It uses a specific verb ('cast your vote') and identifies the resource (candidate drops on a channel), distinguishing it from sibling tools like get_crowd_control (which lists candidates) and play_channel (which plays).

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 description gives explicit usage context: 'Get the channel + candidate trackIds from get_crowd_control first' and explains the token handling options (pass as parameter or set environment variable). It also clarifies the 'NO TOKEN IS NOT AN ERROR' behavior, which is a form of when-not guidance. However, it does not explicitly discuss alternatives or exclusions beyond the prerequisite callback to get_crowd_control.

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