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

With no annotations, the description carries the full disclosure burden. It communicates the destructive nature, the delayed timing, and the confirmation-phrase requirement, but does not state whether the erasure is irreversible or how it can be canceled.

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 wasted words. It packs the action, timing, and the key safety requirement into a compact structure the agent can parse quickly.

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 high-stakes destructive action, the description and schema together are enough to invoke the tool correctly: both required parameters are documented and the purpose is clear. However, with no output schema and no mention of cancellation or post-schedule behavior, the lifecycle around the operation remains incomplete.

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 already fully documents both parameters, including the exact confirmation phrase format and organization_id. The description adds the context that the confirmation phrase gates a scheduled erasure, but it does not add new parameter-level detail 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 names a specific action ('Schedule tenant erasure'), the target resource ('tenant'), and the timing ('after seven days'). It also states the required confirmation gate, which distinguishes it from sibling deletion tools such as commsharbor_deletion_cancel and commsharbor_deletion_request.

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 clearly implies when to use it: when a tenant erasure should be scheduled seven days out. It does not explicitly mention alternatives or exclusions, such as using commsharbor_deletion_cancel to cancel a scheduled erasure.

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