m365_calendar_delete

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the agent is aware this is a destructive write. The description adds 'cancel/delete' which aligns with the annotations, but it does not disclose additional behavioral context such as whether attendees are notified, whether the event is permanently deleted, or any side effects. With annotations covering the safety profile, a score of 3 reflects the minimal extra context.

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, front-loaded sentence that is easy to parse. However, it uses the slash 'cancel/delete' which introduces slight ambiguity, and it lacks any additional detail that could be provided in a second sentence. Still, it is appropriately concise for a simple tool.

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 tool is destructive and has no output schema, the description should provide more context about the effect, such as whether it sends cancellation notifications, if the comment is included in the cancellation message, or what happens after deletion. The description is too minimal to fully inform the agent of consequences, especially with openWorldHint=true suggesting side effects.

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 100%, with both eventId and comment having clear descriptions. The tool description adds no further semantic value beyond what the schema already provides. Since the schema does the heavy lifting, a 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 'Cancel/delete a calendar event' uses a clear verb and resource, distinguishing it from sibling tools like m365_calendar_list, m365_calendar_create, and m365_calendar_update. It precisely indicates the action and target, leaving no ambiguity about what the tool does.

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 does not provide any guidance on when to use this tool versus alternatives. It does not mention that this should be used for removing or cancelling events, nor does it exclude use cases such as updating an event instead. No alternatives or contextual use cases are given.

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