Calendar Delete Event

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

Annotations already indicate the tool is destructive and non-idempotent, so the description's burden is lower, but it still adds no behavioral context such as irreversibility, permission requirements, or consequences of deleting an event. The description merely repeats the tool name.

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 short, but its only sentence is boilerplate that does not earn its place. It is under-specified rather than usefully concise, providing no actionable information for the agent.

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?

Even for a single-parameter tool with an output schema and destructive annotations, the description fails to state the core operation. An agent cannot reliably know from this description that invoking the tool deletes a calendar event, making the definition fundamentally incomplete.

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 0%, so the description carries the full burden of explaining parameter meaning. It says nothing about event_id, its format, how to obtain it, or any constraints. The self-explanatory parameter name does not compensate for the complete lack of description support.

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 only restates the tool name and adds 'Delegated Apple domain tool,' which does not specify what the tool actually does. It fails to explicitly state that it deletes a calendar event, leaving the agent to infer the action from the tool name and title.

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 guidance is provided about when to use this tool versus alternatives such as calendar_update_event or calendar_get_event. The description is purely boilerplate and gives the agent no decision support for selecting among related calendar tools.

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