delete_calendar_event

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

With no annotations provided, the description takes on the full disclosure burden. It explains the dry-run default and returns JSON with details, but does not mention irreversibility, permissions, or behavior on ambiguous matches (e.g., multiple events with same title).

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 front-loaded with the core action, followed by a clean list of arguments and return value. Every sentence adds value with no redundant or verbose phrasing.

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 output schema exists (though not shown), the description appropriately notes the return type. It covers the main parameters and their roles, but could better explain edge cases like multiple matches or calendar_name scope.

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?

The description adds significant meaning beyond the schema: it explains the purpose of each parameter, provides date format hints ('YYYY-MM-DD'), and clarifies the dry_run flag's effect. Since schema coverage is 0%, this compensation is strong, though it could be more explicit about optional filtering behavior.

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 uses a specific verb ('delete') and resource ('Calendar event'), and clarifies it can delete an exact or uniquely matching event. This clearly distinguishes it from sibling tools like 'update_calendar_event' or 'create_calendar_event'.

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 explicit guidance on when to use this tool versus alternatives (e.g., 'update_calendar_event', 'list_calendar_events'). The description does not specify when not to use it or what to do if multiple events match.

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