delete-calendar-event

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

Annotations already indicate destructiveHint=true. The description adds behavioral context: deleting on organizer's calendar sends cancellation messages, and deleting a seriesMaster removes all occurrences. This goes beyond the annotation and provides useful transparency.

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 very concise: three short sentences plus a tip. It is front-loaded with the main action, and every sentence adds value. No unnecessary words.

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 delete tool with 4 parameters and no output schema, the description covers the primary behavior, meeting cancellation effect, and seriesMaster tip. However, it omits details about optional parameters and potential errors, but overall it is complete enough for the core use case.

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?

The input schema has 100% description coverage for all 4 parameters. The description does not add any additional meaning or usage details for the parameters (e.g., If-Match, includeHeaders). Baseline 3 is appropriate since schema is self-explanatory.

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 it removes a specified event from its calendar and mentions the effect of sending cancellation messages for meetings. The tip about seriesMaster vs single occurrence adds clarity but does not explicitly differentiate from siblings like 'delete-specific-calendar-event'.

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 tip provides guidance on when to delete a seriesMaster vs a single occurrence, implying usage scenarios. However, there is no explicit statement about when to use this tool versus alternatives like 'cancel-calendar-event' or 'delete-specific-calendar-event', nor any when-not-to-use conditions.

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