Delete Event

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

The description adds no behavioral context beyond what the annotations already provide (destructiveHint=true, readOnlyHint=false). It does not mention permanence, side effects, or any consequences of deletion. With annotations already labeling the operation as destructive, the description contributes little additional information.

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 a single sentence with no unnecessary words. It stays focused and front-loaded, clearly stating the core action without redundancy.

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 simple delete tool with one parameter, the description and schema provide sufficient context. The annotation destructiveHint=true already alerts the agent to the destructive nature. The parameter description tells how to source the event handle. While a note about irreversibility would be nice, the existing structured data covers the essentials, making this reasonably complete.

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 provides full coverage (100%) with a clear description for the only parameter: 'Event handle from list-events: the URL in cloud mode, the UID in local mode'. The tool description itself adds no extra meaning beyond the schema, so the baseline of 3 is appropriate.

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 tool's function with a specific verb and resource: 'Deletes a calendar event'. This directly distinguishes it from sibling tools like create-event, update-event, and list-events.

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 no explicit when-to-use or alternative guidance. Usage is implied by the tool name and the parameter description that mentions getting the event handle from list-events, but there is no explicit context or exclusion. The need to first call list-events is hinted at in the schema, not in the main description.

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