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

With no annotations, the description must carry the full behavioral burden, and it does supply real context: the vote is Lightning-funded and will verify npub membership, validate election activity, and record a payment proof. Most importantly it honestly discloses 'Not yet implemented', which is decisive for an agent. It stops short of describing permissions, payment amounts, or failure modes.

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?

Two short sentences, front-loaded with the core action and the vote's funding mechanism. No filler. The implementation-status caveat is placed second, which is arguably the right order for an agent scanning for feasibility.

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?

An output schema exists, so return-value explanation is not owed. The unimplemented status is disclosed, which is essential. But for a 3-parameter mutation with zero schema coverage, the description leaves parameter semantics and payment/permission requirements unexplained, so it is only minimally complete.

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?

Three required parameters at 0% schema description coverage, and the description explains none of them. Only npub is obliquely glossed ('verify npub membership'); election_id and, critically, the vote value's accepted form are left entirely undefined, so an agent cannot construct a valid call.

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 (cast) and resource (Lightning-funded ban vote) scoped to an active ban election. It is clearly distinguishable from siblings like check_ban_status, initiate_ban_election, and confirm_citizenship. Slightly held back because it never spells out the relationship to initiate_ban_election beyond the shared 'ban election' domain.

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 'active ban election' qualifier implies a precondition, but there is no explicit when-to-use guidance, no when-not-to-use, and no named alternative among the 30 siblings (e.g., check_ban_status before voting). Usage is inferrable but not stated.

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