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

With no annotations, the description carries the behavioral burden and does disclose a non-obvious trait: one vote per network and re-voting replaces the previous vote, which tells the agent the operation is effectively idempotent per network rather than additive. It still omits whether membership/auth is required to vote, but the replacement semantics are genuinely valuable context beyond the schema.

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, action first, behavioral caveat second. Nothing is padded and every clause carries information.

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 two-parameter, no-annotation, no-output-schema mutation, the description covers the action, the target constraint, and the repeat-vote behavior. It would be fully complete with a note on voting eligibility and whether a vote can be withdrawn, but the core is sufficient 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 coverage is 100%, so the baseline is 3, and the description adds real meaning on top: suggestion_id must reference an *approved* suggestion, a constraint the schema's "sug_..." hint does not convey. The up/down value space is already fully documented in the schema, so no further credit is warranted there.

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 verb (vote) and resource (council suggestion) with a scope qualifier ("approved"), which cleanly separates it from council_suggest (create) and council_comment (discuss). An agent can identify the action and target without opening the schema.

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 phrase "on an approved council suggestion" implies the prerequisite that the target must already exist and be approved, which is useful implicit guidance. However, it never states when to vote versus when to use council_comment, nor what to do if the suggestion is not yet approved. Usage is implied rather than explicit.

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