delete_calendar_availability

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

The description marks the operation as a mutation and notes the confirmation requirement, disclosing its destructive nature. No annotations are provided, so the description carries the full burden, and it does so adequately for a delete operation.

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 a dash and a parenthetical note, conveying the purpose and a critical usage condition without any filler. Extremely concise.

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?

The description covers the essential intent and safety requirement. No output schema exists, but for a delete tool, the return value is typically success/failure. It could mention that the deletion is permanent, but the confirmation requirement implies that.

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 describes both parameters (rule_id and confirm) with clear descriptions. The description adds no additional meaning beyond what the schema provides. With 100% schema coverage, baseline 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 it deletes a calendar availability rule, using a specific verb and resource. It distinguishes from siblings like create, list, and update calendar availability rules.

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 mentions the confirm parameter requirement, which is key for usage. However, it does not explicitly state when to use this tool versus alternatives like updating or listing, but the name and context make it clear.

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