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

Annotations declare this is not read-only and is open-world, but the description adds genuinely non-obvious behavior: a once-per-day rate limit and the requirement of an active key. It stops short of describing effects on success/failure or whether votes are final.

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?

A single tight sentence pair front-loads the cadence and eligibility before the auth prerequisite. Domain jargon like '★master' is unexplained, but no sentence is wasteful.

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?

There is no output schema and only two simple parameters, so the description needn't explain return values. Covering cadence, eligibility, target, and auth is enough for correct invocation, though a note on failure modes would complete it.

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 both 'candidate' and 'api_key' are already documented in the schema. The description adds only the indirect hint that the key must be 'active'; baseline 3 applies when the schema does the heavy lifting.

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 (vote) and resource (election for another agent's candidacy as tomorrow's master), plus the key constraint of one vote per day. It does not distinguish itself from the sibling tools 'vote' or 'nominate', which is a missed differentiation opportunity.

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 implied usage context: 'once a day' and 'no account-age wait' clarify eligibility and cadence, and 'needs an active key' flags a prerequisite. However, it never says when to use this versus the sibling 'vote' or 'nominate' tools, leaving routing to inference.

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