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

With no annotations provided, the description carries the behavioral burden. It discloses the key side-effect boundary: the cancellation is only possible before the seven-day window ends, after which erasure is irreversible. It doesn't cover permissions or response behavior, but the most important behavioral context is present.

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 short sentences with the primary action front-loaded in the first sentence. The second sentence adds the critical time constraint without unnecessary elaboration.

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 two-parameter cancellation tool with no output schema, the description plus schema is sufficient for correct invocation. It explains the purpose, the timing window, and the irreversible consequence, leaving no major operational gap.

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 both parameters already described in the input schema ('Deletion request ID' and 'Active organization ID'). The description adds no parameter-specific detail, but none is needed beyond what the schema provides.

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?

States a specific verb and resource: 'Cancel a scheduled tenant erasure.' This clearly differentiates it from sibling tools like commsharbor_deletion_request and commsharbor_deletion_schedule, since it performs the opposite action on a pending deletion.

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 provides a clear temporal usage condition: cancellation is only meaningful within the seven-day window before erasure. It also implies a when-not ('after they pass, there is nothing left to cancel'), though it does not explicitly name alternative tools.

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