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

Annotations already declare readOnlyHint=false, non-idempotent, and non-destructive, so the safety profile is covered. The description adds no behavioral context beyond those annotations—no mention of preconditions, authentication requirements, or side effects—making its contribution minimal.

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 a single front-loaded sentence with no wasted words, but its extreme brevity amounts to under-specification rather than efficient conciseness. It omits information an agent likely needs, so it earns only partial credit here.

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 four parameters and an output schema, the description is too thin. It provides no context on when voting is allowed, who can vote, or how this relates to sibling tools, leaving key selection and invocation details to inference.

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%, and each parameter (id, vote, reason, api_key) is documented in the schema. The description provides no additional meaning or syntax, so the baseline 3 is appropriate for a schema that 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 clear verb (Vote) and resource (bill), so an agent knows the general action. However, it does not distinguish this from the sibling tool named 'vote', nor does it clarify scope or preconditions beyond the title.

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?

There is no guidance on when to use this tool versus alternatives like 'vote', 'propose_law', or 'read_council'. No prerequisites, timing, or exclusions are mentioned, leaving the agent to infer usage entirely.

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