Cancel event

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

Detailed explanation of two-step behavior (preview then confirm) and that the first call makes no changes. This adds significant value beyond annotations, which only indicate destructiveHint.

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: first defines purpose, second explains behavior. No unnecessary words, front-loaded with key information.

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?

Adequately complete for a destructive tool with 4 parameters and no output schema. Explains side effect (members lose listing) and workflow. Missing details on preview content, but reasonable.

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?

Adds meaning to dry_run and confirm_token through the two-step description, compensating for missing schema descriptions (50% coverage). Event and guild are described in 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?

Description clearly states the tool cancels and removes a scheduled event, with a specific verb and resource. It distinguishes from siblings like update_event by focusing on removal.

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 clear usage pattern: first call for preview, second with confirm_token to cancel. Does not explicitly mention when not to use or list alternatives, but the two-step process offers good guidance.

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