events_delete

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

Annotations already mark the tool as destructive, but the description adds crucial context: "DESTRUCTIVE - IRREVERSIBLE" and the dry-run/confirmation requirement (__confirm:true and MCP_DRY_RUN=false). This goes beyond the annotations and is highly valuable for safe invocation.

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 well-structured with bold headings (Purpose, When to use, Returns) and every sentence carries essential information. It is compact with no fluff.

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?

The description covers purpose, usage guidance, safety/confirmation requirements, and return value. With output schema present, it doesn't need to detail return shape. It is complete for a destructive tool with the given annotations and schema.

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%, so the description doesn't need to repeat parameter meanings. The description does mention __confirm and MCP_DRY_RUN, but the schema already covers these. No additional parameter-level insight is provided beyond what the schema gives.

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 clearly states the verb and resource: "Delete a scheduled event." It also distinguishes this from modifying an event by contrasting with setting status=4, which is a different sibling tool behavior.

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 explicitly provides a "When to use" section and gives an alternative (vs. setting status=4 that keeps the record). This helps the agent choose between events_delete and events_modify.

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