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

With no annotations, the description carries the full burden of behavioral disclosure. It does reveal that the tool can both create and update a ballot and that governance is community-defined, but it omits important behavior such as whether votes can be changed or withdrawn, what happens to existing ballots, and any required permissions.

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 concise and front-loaded with the core action. The second sentence adds a small amount of context about governance, though it is somewhat vague. Overall, it is appropriately short and free of filler.

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 three-parameter tool with no parameter descriptions, no output schema, and no annotations, this description is not complete enough. An agent would not know what to pass for choice, what the response looks like, or what constraints or side effects apply. The community-defined governance note is too thin to cover those gaps.

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 0%, so the description must compensate, but it does not explain any parameter. The meaning of debate_id, the expected format of choice, and the role of rationale are all left unspecified. The term 'ballot' weakly hints at choice, but that is not sufficient for correct invocation.

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 uses a specific verb and resource: 'Cast or update a raw ballot.' This clearly distinguishes the action from sibling tools like propose, argue, and amend, which have different purposes. The term 'raw ballot' is slightly vague but enough to convey the core function.

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 provides no explicit guidance on when to call vote versus siblings like propose or amend. The phrase 'Governance rules remain community-defined' implies the caller must consult external rules, but it does not state when this tool is appropriate or when alternatives should be used.

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