delete_event

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

Annotations already disclose idempotent and destructive traits, so the bar is lower. The description adds the context that deletion is by ID and within the training calendar, but doesn't add details beyond that. 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 concise, front-loaded with the action, and follows a clear structure (purpose, usage, args). Every sentence earns its place without unnecessary filler.

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 two parameters, complete schema coverage, an output schema, and annotations covering safety, the description plus structured data are sufficient to select and invoke the tool correctly.

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 parameters fully described. The description repeats the argument names and defaults but adds no new semantic information beyond what the schema already provides.

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 'Delete a calendar event or planned workout by ID' with a specific verb and resource, and distinguishes itself from sibling tools like delete_activity by focusing on calendar events/workouts.

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 provides explicit usage context: 'Use to remove canceled workouts or events from the training calendar.' While it doesn't explicitly mention alternatives, the distinct resource (events vs. activities) is clear from the sibling tool names and the description.

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