Delete Calendar

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

With no annotations, the description must disclose behavior fully. It does state the significant side effect that deleting the calendar also deletes its events, which is useful. However, it does not mention irreversibility, permission requirements, or other potential impacts like shared access removal, leaving gaps in transparency.

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 core description is a single, front-loaded sentence: 'Delete an additional calendar and its events.' It is concise and free of fluff. The Chinese intents line is a compact, purposeful addition for multilingual support without redundancy.

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 operation with one parameter, the description is mostly complete. It covers the primary action and the cascade to events. However, it lacks an explicit warning about permanence or any prerequisites. Since there is no output schema and the main effect is clear, it is reasonably complete but could be stronger.

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 provides 100% coverage with a clear description for calendarId ('Calendar ID to delete.'). The tool description adds no further meaning, format, or usage detail for the parameter. Per the rubric, with high schema coverage, a baseline of 3 is appropriate.

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 tool's action with a specific verb ('Delete') and resource ('calendar'), and adds the key detail that it also deletes the calendar's events. This distinguishes it from sibling tools like calendar_delete_event and calendar_update_calendar. The qualifier 'additional' also hints at scope, making the purpose unambiguous.

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 no explicit guidance on when to use this tool versus alternatives. It does not mention that deleting individual events should use calendar_delete_event, nor does it state restrictions (e.g., primary calendar cannot be deleted). The context is implied but not spelled out, leaving the agent to infer usage.

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