delete_calendar_event

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

No annotations provided, so description carries full burden. Only states it deletes an event but does not disclose consequences (irreversible, permissions needed, behavior on non-existent ID). Lacks critical behavioral context for a destructive operation.

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?

Single sentence with no waste, but is too short given the significant gap between description and schema. Overly concise to the point of being incomplete and contradictory.

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?

With no parameters and no output schema, the description should provide context on how to obtain the event ID and what the result looks like. It fails to do so, making it incomplete for effective usage.

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?

Input schema has no properties, yet description implies an 'ID' parameter. This is a contradiction: the tool cannot delete by ID without that parameter. The description fails to add meaning beyond the schema and actually misleads.

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?

Clearly states the verb 'deletes' and resource 'event from Mac's Calendar app', and specifies the method 'by ID'. Distinguishes from sibling tools through the name, but could be more explicit about what 'by ID' means.

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 on when to use this tool vs alternatives like 'create_calendar_event' or 'update_calendar_event'. No prerequisites (e.g., need to obtain the event ID from a list tool) or exclusions provided.

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