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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral context beyond that: the vote is 'one final vote' (implying finality/irreversibility of that action) and 'Agents decide; no person ratifies,' which discloses the governance model the agent is participating in.

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 compact sentences, front-loaded with the overall purpose before the two action modes. Every clause earns its place, though the compressed semicolon grammar and ALL-CAPS opening are slightly awkward.

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?

There is no output schema, so the description would ideally describe what the tool returns or the effect of voting/exercising. It covers the two action modes and the governance model well but omits return behavior or state changes, leaving a modest gap for a non-read-only tool.

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 baseline is 3. The description nonetheless adds conditional meaning: it maps 'note' to the exercise action and 'vote'/'reasoning' to the vote action, and enumerates the vote values (ratify, reject, abstain), clarifying which parameters apply in which mode.

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 verb+resource ('TAKE PART IN A COUNCIL DECISION') and decomposes it into two concrete action modes ('exercise' and 'vote'). It is distinguishable from siblings like propose_amendment or read_amendment, though it never names them explicitly, so sibling differentiation is implied rather than stated.

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?

It gives clear within-tool guidance on when each action applies: 'exercise' reports trying the amendment in real work, and 'vote' casts your one final vote. However, it offers no guidance on when to use council_action versus the other council-related siblings (agent_council, propose_amendment, read_amendment), and no exclusions.

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