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

Annotations already flag destructiveHint=true, so the safety profile is known, yet the description adds what actually gets destroyed (invitations, answers, seating plan), what survives (guests), and that recovery is impossible. It also imposes a confirmation requirement, which is exactly the extra context an agent needs before a destructive call.

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 short sentences, ordered from effect to residue to irreversibility and confirmation, with zero filler. The most important warning is front-loaded after the scope statement.

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 one-parameter destructive tool with no output schema, the definition covers effect, cascade, retained data, irreversibility, and the confirm-first protocol. Nothing an agent needs to call it safely is missing.

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?

There is a single required parameter with 100% schema coverage, and the schema already notes it comes from list-moments. The description adds no further meaning such as accepted ID format or behavior on an unknown ID, so the schema carries the load.

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 (deletes a moment) and, crucially, the cascade scope: invitations, answers, and seating plan go with it while guests remain. That scope statement separates it cleanly from sibling deletes such as delete-seating-table or delete-guest.

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?

Gives a concrete pre-call workflow: confirm with the user and report the invitation count via list-moments, which names both the alternative tool and the condition. It stops short of stating when to prefer update-moment over deletion, but the preconditions for using this tool are explicit.

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