Delete AddEvent Calendar

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

The description goes beyond the destructiveHint annotation by disclosing permanence ('cannot be undone'), the cascading effect on events, and specific error handling (404). This adds valuable operational context.

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 well-organized with clear sections for Args, Returns, Examples, and Error Handling. It is concise but the Returns line ('A confirmation message') adds little value and the Args section duplicates schema information.

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 1-parameter delete tool without an output schema, the description covers the essential context: purpose, permanence, cascading effects, return type, error behavior, and a pre-check recommendation. It is sufficiently complete.

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 already provides 100% coverage and a detailed description for calendar_id. The description's Args section merely restates the parameter with less detail, adding no new meaning.

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 'Permanently deletes a calendar' with a specific verb and resource, and further clarifies that it affects events on the calendar. This distinguishes it from related tools like addevent_delete_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?

The example suggests calling addevent_search_events first to check events, providing practical guidance. However, it doesn't explicitly state when not to use this tool or name alternatives for calendar deletion.

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