calendars_delete_calendar

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

The description adds no behavioral context beyond what the annotations already declare (destructiveHint: true, idempotentHint: true). It does not mention permanence, side effects, or required permissions. With annotations present, the bar is lower, but the description still fails to add any extra value.

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 extremely concise—a short verb-object phrase with no unnecessary words. However, it's so minimal it borders on being under-informative. It is well-structured and front-loaded, but could benefit from a bit more context.

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 tool with one parameter, the description plus annotations (destructive, idempotent) is minimally sufficient. But it lacks any explanation of return values or confirmatory behavior, and given the large sibling set, a bit more context would help an agent avoid misuse.

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 schema covers 100% of the parameter (calendarId has a description 'Calendar Id'), so the schema itself documents the parameter adequately. The description does not add any further meaning or format details, making the baseline 3 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 'Delete Calendar' clearly states the verb and resource. It is distinct from sibling tools like calendars_delete_schedule and calendars_delete_calendar_resource, though it lacks explicit differentiation. The purpose is unambiguous but could be more specific about the calendar entity type.

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 guidance is provided on when to use this tool versus alternatives like calendars_delete_schedule or calendars_update_calendar. There is no mention of prerequisites, conditions, or exclusions, leaving the agent to infer usage solely from the name.

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