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

Adds meaningful behavior beyond annotations: ballots are additive, manageToken is required, and the whole batch is rejected if any voter already voted electronically. This is strong operational context even though annotations already declare non-readOnly, non-idempotent behavior.

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?

Six short, front-loaded sentences with no filler. The key requirement, failure mode, and token prerequisite are each stated once and clearly.

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 mutation tool with no output schema, the description covers the essential prerequisites, required evidence, and batch-rejection risk. It could say more about the success response or retry implications, but an agent has enough to call it 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 schema already documents meetingId, manageToken, voters, and evidenceImageDataUrl. The description reinforces the required evidence photo and one-voter-equals-hash-plus-choices model, but adds little syntax or format detail beyond the schema.

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 action and resource: entering written resolution ballots (on-site paper votes). It is clear enough to distinguish paper-ballot entry from electronic voting siblings, though it does not explicitly name an alternative tool.

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 implies when to use it (paper/on-site ballots) and gives an important exclusion (do not mix in people who voted electronically), but it does not explicitly name the alternative electronic voting tool or state when-not-to-use conditions beyond that warning.

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