delete_calendar_event

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

The description says 'with preview' but does not explain what the preview entails, whether deletion is reversible, or if confirmation is required. No annotations exist to compensate, leaving the agent uncertain about side effects.

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 extremely concise (five words), but at the cost of completeness. It is front-loaded but lacks critical details that could be added without becoming verbose.

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?

Given the destructive nature of deletion and zero parameters, the description is insufficient. It does not explain context requirements, output, or error scenarios, leaving the agent underinformed.

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 zero parameters, and the description does not clarify how the target event is identified (e.g., via context or selection). Schema coverage is 100% but empty, so the description should provide guidance but fails to do so.

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 'Delete' and resource 'calendar event', distinguishing from sibling tools like create or update. The phrase 'with preview' adds a nuance but is ambiguous, slightly reducing clarity.

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?

No guidelines on when to use this tool versus alternatives. It does not specify prerequisites (e.g., event must exist) or when not to use it, such as if the event is recurring or shared.

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