Delete Calendar

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

Annotations indicate destructiveHint=true and idempotentHint=true. The description adds context: the action is permanent, cannot be undone, and the confirm parameter prevents accidents. Also explains the error when trying to delete the default calendar.

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?

Well-structured with a prominent warning emoji, clear sections for args, returns, and raises. Every sentence adds value, and the warning is front-loaded. No unnecessary words.

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?

Covers all essential aspects: preconditions (default calendar not deletable), required confirmation, permanent nature, and error cases. The output schema (not shown) is likely sufficient, and the description explains return type and raises. Complete for this destructive operation.

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 input schema has 0% description coverage, but the description fully explains each parameter: account_id, calendar_id, and confirm (with its role in preventing accidents). Provides clear semantics beyond 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 clearly states the action: 'Delete a calendar permanently.' It specifies the resource (calendar) and includes a warning about data loss. Distinguishes from sibling tools like calendar_create_calendar and calendar_delete_event by focusing on calendar 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?

Explicitly notes that the default calendar cannot be deleted and requires user confirmation via the 'confirm' parameter. However, no explicit alternatives are given for cases where deletion is not intended, though siblings provide other calendar operations.

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