calendars_delete_event

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is known. However, the description adds no behavioral context beyond these flags—no mention of irreversibility, cascade effects, or any side effects. It fails to add value beyond what structured fields already provide.

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 brief, but this is under-specification rather than effective conciseness. It lacks any structure or substantive information, making it unhelpful for an agent. It is not 'front-loaded' with key details because there are no details at all.

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 operation with a nested object parameter and no output schema, the description is severely incomplete. It omits any information about return values, error conditions, or special cases like recurring events. The tool's complexity demands more context than a single phrase.

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 descriptions are thorough, covering both body and eventId with a useful note on recurring events. Since schema coverage is 100%, the description does not need to add parameter details, and its silence here is acceptable. It meets the baseline for high coverage.

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 'Delete Event' is a direct restatement of the tool name, providing no additional context or differentiation from similar calendar delete tools like calendars_delete_schedule or calendars_delete_calendar. It is a tautology that does not help an agent understand the specific resource being acted upon.

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 offers zero guidance on when to use this tool versus alternatives. There is no mention of scenarios, prerequisites, or distinguishing factors from other delete operations, leaving the agent to guess based solely on the name.

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