delete-specific-calendar-event

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

Annotations already mark destructiveHint=true and readOnlyHint=false. The description adds critical context about seriesMaster deleting all occurrences, which goes beyond annotations and informs the agent of cascading behavior.

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 and includes a helpful tip, but the first sentence 'Delete navigation property events for me' is somewhat redundant and could be more direct. Overall, it's efficiently structured.

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?

No output schema exists, but the description captures the key behavioral nuance (seriesMaster deletion). It does not discuss return values, but for a delete operation this is acceptable given the destructiveHint and openWorldHint annotations.

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 coverage is 100%, so baseline is 3. The description adds value by explaining the semantic difference between eventId for a seriesMaster vs an instance, which is not in the schema.

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 explicitly states 'Delete navigation property events' and provides a tip clarifying the effect on seriesMaster events. This differentiates it from siblings like 'cancel-calendar-event' or 'delete-calendar-event', though the phrase 'for me' is somewhat vague.

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 offers clear guidance: deleting a seriesMaster deletes all occurrences, and to cancel a single occurrence use the specific instance ID. It implicitly contrasts with other tools for partial deletion.

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