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

Annotations are absent, so the description carries the full burden. It discloses immutability and mentions enforcement of scope, activation, account age, conflicts, and private evidence consent. This adds some behavioral context, but it fails to describe the response format, error behavior, or further side effects, which are critical for a write operation.

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 single sentence is concise and waste-free, but it lacks any structure. It front-loads the verb but doesn't provide a logical breakdown of scope or parameters. It's appropriate in brevity but not in completeness.

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 complexity (nested objects, three required parameters, no output schema, no annotations), the description is severely inadequate. It leaves out critical information about parameters, usage context, enforcement details, and expected outcomes, making it far from sufficient for correct invocation.

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?

With schema description coverage at 0%, the description must compensate by explaining parameters. It says nothing about 'id', 'vote', 'idempotencyKey', or the nested fields like 'decision', 'rationale', 'evidenceIds', and 'expectedVersion'. An agent has no idea what values are expected or how they relate, making this a severe gap.

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 states a specific action 'Submit an immutable case ballot and rationale' with a clear resource (case ballot). It conveys the core purpose without being tautological. However, it does not explicitly distinguish this from siblings like submit_evidence or open_evidence_case, so it's clear but not fully differentiated.

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?

No guidance is provided on when to use this tool versus alternatives such as submit_evidence, list_adjudication_cases, or read_adjudication_case. There is no mention of conditions, prerequisites, or exclusions. The agent receives no contextual roadmap for choosing this tool.

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