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

The description says 'Delete' which is a destructive action, but the annotations declare destructiveHint=false. This is a direct contradiction. Additionally, the description provides no context about irreversibility, permissions, or effects on related data. The contradiction alone forces a score of 1.

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 a single sentence with no wasted words, front-loading the core action. However, it is so minimal that it provides little information, though for a simple delete tool this is adequate. Not a 5 because it lacks any helpful 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?

This is a destructive operation with no annotations, no output schema, and a very short description. It fails to disclose that deletion is permanent, what happens to associated events, or any edge cases. The low complexity does not compensate for the lack of critical information.

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 100% description coverage for both parameters (calendarId and overrideId). The description adds no extra meaning beyond what the schema already provides, so the baseline of 3 applies.

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 states the exact action ('Delete') and resource ('an availability override'), which clearly distinguishes it from sibling tools like create_calendar_override or get_calendar_overrides. Even without the tool name, the purpose is 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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, when deletion is appropriate, or any excluded scenarios. The only usage context is implicit from the tool name and sibling names.

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