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

No annotations exist, so the description carries the full behavioral burden. It discloses a major hidden consequence: guests are emailed a cancellation that cannot be undone. This is strong transparency for a delete operation, though it could also clarify series vs. single-occurrence behavior in more detail.

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?

Three short sentences with no filler. The action is front-loaded, followed by the irreversible side effect, then the required user confirmation. Every sentence earns its place.

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 the essential context for a delete tool: what is deleted, the external notification side effect, irreversibility, and the need for user confirmation. However, the optional calendarId parameter and expected response behavior are not addressed, and there is no output schema to fill that gap.

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 only 33%: only mailbox has a description. The description does not explain eventId or calendarId, their formats, or their relationship to deleting an event vs. an occurrence. With low schema coverage, the description should compensate but does not.

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 states the specific action 'Delete' and the resource 'Google Calendar event', with the added nuance 'one event or one occurrence'. This clearly distinguishes it from siblings like delete_google_calendar and delete_outlook_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 description gives explicit pre-call guidance: 'Ask the user to confirm before calling this.' This is important for a destructive operation. It does not explicitly name alternative tools like update_google_calendar_event or move_google_calendar_event, so it lacks exclusion guidance.

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