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

The annotations already mark this as destructive and non-idempotent, and the description adds substantial concrete behavior: page, guest list, photos, and messages are permanently gone; guests may be notified; only hosts can do this; calls require confirmation/owner approval. These details go well beyond the structured hints.

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 front-loaded with the core destructive action and consequences, then covers the alternative, permissions, and confirmation behavior. Each sentence contributes distinct operational information for a high-stakes deletion tool.

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 description provides the necessary consequences, alternative action, authorization constraints, and approval behavior. There are no material gaps for correct selection or invocation.

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 description coverage is 100%, and the single parameter is already documented as “event_id from list_events.” The description does not add further syntax or selection guidance for event_id, so the baseline 3 is appropriate.

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 uses a specific verb and resource, names the exact scope (“event you host for everyone, with its guest list”), and explicitly distinguishes this destructive action from cancel_event. An agent can identify what it does and which sibling preserves the page instead.

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?

It states the key condition for use versus the alternative: use this to permanently delete the event page and guest list, but use cancel_event to keep the page and notify guests. It also adds host-only authorization and confirmation/approval context.

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