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

Goes well beyond the annotations by naming exactly what survives the cancellation: existing messages, private membership, receipts and consumed funds — which substantiates the destructiveHint=false / idempotentHint=true profile rather than merely restating it. It also declares the required write scopes and the idempotency_key obligation, so an agent understands both blast radius and prerequisites.

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 tight sentences with the primary effect front-loaded, then preservation semantics, then the alternative and preconditions. Dense but every clause carries information; no filler.

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 3-param mutation with no output schema, the description covers safety-relevant behaviour, auth scopes and idempotency well. The remaining gap is the idempotency/retry semantics of an already-cancelled thread and any hint about what the call returns, plus the unexplained reason field.

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 only 33%, so the description should compensate, and it does not: thread_id and the nested input.reason (a required free-text justification, 1-500 chars) are never explained. The one parameter it does mention, idempotency_key, is already fully documented in the schema, so the description adds almost nothing beyond structured fields.

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?

Concrete verb + resource: stops new assistance/publication and cancels pending bound resident requests, which is far more informative than a tautology of the title. It does not clearly separate itself from the sibling cancel_resident_request, which sits in the same neighbourhood, though it does route membership revocation to collaboration_member.

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 context of use is stated (stop assistance/publication, cancel pending bound requests) and one explicit exclusion is given: use collaboration_member to revoke membership instead. Missing is any when-not guidance for cancel_resident_request or an indication that this applies only to already-open investigations.

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