calendar_delete_calendar

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

The description discloses critical behavioral traits: irreversibility (IRREVERSIBLE), known unreliability via scripting, expect PLATFORM_LIMITATION error, and fallback manual deletion. This goes well beyond the annotations (destructiveHint=true) by adding concrete failure scenarios and mitigation.

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 'IRREVERSIBLE', and includes essential warnings and usage notes. It could be slightly more structured (e.g., separate lines for each point), but remains efficient and scannable.

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 tool with no output schema, the description covers the core action, side effects, parameter nuances, and fallback behavior. Missing details like exact return value or alternative error handling, but overall adequate.

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 meaning beyond the input schema: it clarifies that confirm must be set to true ('Requires confirm:true') and that calendarIndex is for disambiguating duplicate names. With schema coverage at 67%, this compensates for the missing description on the confirm parameter.

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 'Permanently delete a calendar and everything in it,' which clearly identifies the action and resource. It distinguishes from sibling tools like calendar_delete_event by focusing on calendar-level deletion.

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 usage context: requires confirm:true and suggests using calendarIndex for disambiguation when names are duplicated. It also warns about potential PLATFORM_LIMITATION errors and recommends a manual fallback. However, it does not explicitly contrast when to prefer this over other deletion tools.

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