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

Annotations already indicate non-read, idempotent, and non-destructive. The description adds the timing constraint (cooling-off window) but no additional behavioral traits like auth requirements or side effects.

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?

The description is a single, front-loaded sentence with no unnecessary words. Every part is essential.

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 description is complete for a simple cancellation operation. Output schema exists (handling return values), and the description covers the critical context of the cooling-off window.

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% with a clear description for the single required parameter ('slug'). The description adds no new information about parameters 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 clearly states the action ('Withdraw'), the resource ('scheduled org deletion'), the context ('during the cooling-off window'), and the actor ('owner'). It effectively distinguishes this tool from siblings like colony_org_request_deletion and colony_org_deletion_status.

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 implies when to use (during cooling-off window, by owner) but does not explicitly state when not to use or provide alternatives. However, it gives sufficient context for correct selection.

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