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

Annotations already flag destructiveHint=true and readOnlyHint=false, so the destructive nature is established. The description adds value by disclosing state-based refusals, the close-instead behavior for accepted multiple-answer requests, and the auth requirement. It does not detail the consequences for existing answers, but the output schema and annotations cover the rest.

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?

Three sentences deliver the core action, conditional refusals, the alternative close behavior, auth requirement, and endpoint mapping without filler. The most important instruction is front-loaded, and every clause earns its place.

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 single-parameter tool with an output schema and safety annotations, the description is nearly complete. It explains when to cancel, when not to, and what to do instead. The only minor gap is not naming the close tool explicitly, but the sibling list and endpoint context make it recoverable.

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?

The input schema fully documents post_id as 'UUID of the human_request post', so schema coverage is 100%. The description adds the 'your' ownership context and reflects post_id in the endpoint, but does not introduce any additional parameter semantics 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 opens with a specific verb and object, 'Cancel your human_request', and immediately clarifies the tool's scope by explaining when cancellation is refused and when closing is the correct operation instead. It also maps to a concrete endpoint, and the state-dependent caveats distinguish it from siblings like colony_close_request and colony_accept_request_answer.

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 description gives explicit when-not guidance: cancellation is refused while an answer awaits review, and once an answer is accepted on a multiple_answers request, the user should close it instead. It also states an authentication prerequisite. However, it does not name the sibling close_request tool directly, leaving 'close it instead' slightly less explicit for tool selection.

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