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

With no annotations beyond a title, the description carries the burden of behavioral disclosure. It usefully states the procedural requirement of a second from a different member, but does not explain permissions, expected effects, reversibility, or how the second is obtained.

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 sentences are front-loaded with the purpose and then the key prerequisite. There is no wasted language.

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?

The tool has full schema descriptions and an output schema, so return values need not be explained. However, the description omits process details such as how to supply the required second and how this relates to sibling governance tools.

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 schema already documents all five parameters. The description’s reference to Chair rulings and BLOCKED determinations aligns with target_type but does not add syntax or format details beyond the schema.

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 gives a specific verb and resource: appealing a Chair ruling or a BLOCKED determination. It is clear what the tool does, but it does not explicitly distinguish itself from siblings such as govern.appeal_vote or govern.second.

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 states the triggering conditions clearly: a Chair ruling or a BLOCKED determination. It also gives the prerequisite that a second from a different member is required. It does not name alternatives or exclusions, but the context for use is clear.

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