delete-specific-calendar-event

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, confirming a write operation. The description adds behavioral context: the tip about seriesMaster behavior and using instance IDs. This goes beyond the annotations by explaining a key destructive consequence. No contradiction with annotations.

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 concise with two sentences. The tip is front-loaded and provides critical information without unnecessary verbosity. Every word 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?

For a destructive delete tool with no output schema, the description adequately covers the most important behavioral aspect (seriesMaster deletion). However, it lacks mention of typical success/error responses (e.g., 204 No Content) and potential error conditions. Still, it is reasonably complete for the complexity.

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?

All 5 parameters have descriptions in the input schema, achieving 100% coverage. The description does not add additional meaning beyond the schema; the tip indirectly relates to 'eventId' but does not explicitly explain parameter usage. Baseline score of 3 is appropriate given full schema 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 name 'delete-specific-calendar-event' clearly indicates the action and resource. The description adds 'Delete navigation property events for me', which is somewhat technical but still conveys the purpose. However, it does not explicitly distinguish this from sibling tools like 'delete-calendar-event' or 'cancel-calendar-event', which could cause confusion.

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 tip provides partial guidance: it warns that deleting a seriesMaster deletes all occurrences and suggests using a specific instance ID to cancel a single occurrence. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention prerequisites or context such as required permissions.

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