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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety class is known; the description adds value beyond that by naming the cascade ('with its answers and seats') and stating 'Cannot be undone'. What remains unstated is behavior on an invalid or already-deleted id. No contradiction with annotations: 'Removes' matches destructiveHint=true.

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 sentences, no filler, with the destructive scope and the irreversibility warning front-loaded so the agent reads the risk before anything else. Every clause carries information the agent needs.

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 and annotations that already flag destructiveness, the description covers the essential cascade and irreversibility. Only minor gaps remain, such as error behavior for a missing invitation, which is not strictly needed to invoke it correctly.

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% and the single 'id' property already documents that it is an integer invitation id sourced from search-guests. The description adds no further meaning about the identifier (e.g., invitation id vs. guest id), so it sits at the baseline where the schema does the work.

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?

Specific verb ('Removes') plus a precise resource ('an invitation from the guest list') and scope (its answers and seats), which separates it from add-guest/get-guest/update-guest and from the other delete-* tools by resource. It stops short of explicitly contrasting removal of the invitation with sibling operations like unseat-guest, which an agent might otherwise confuse.

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?

Provides one real usage rule -- 'confirm with the user first' -- which tells the agent this needs a confirmation gate before invocation. It gives no guidance on when a guest should be removed versus merely unseated or updated, so the when-to-use decision against siblings is left implicit.

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