unschedule_draft_plan

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

The description adds behavioral context beyond the destructiveHint annotation by specifying what is deleted (calendar copies) and what is preserved (library plan). However, it does not disclose behavior such as what happens if no calendar copy exists, potential cascading effects, or rate limits.

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 fluff, which is concise. However, given the lack of parameter descriptions and the complexity of the operation, the description is under-specified and fails to convey necessary 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?

Despite having an output schema, the description does not mention return values or side effects beyond deletion. With 4 parameters and no parameter descriptions, the description is incomplete for an agent to use the tool correctly.

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?

No parameter descriptions are provided in the schema (0% coverage), and the tool description does not explain the meaning or purpose of any parameter (plan_id, expected_hash, start_date, confirmed). The agent receives no guidance on how to populate these fields.

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 uses a specific verb ('Delete') and target ('calendar copies from one managed plan application'), clearly distinguishing this tool from siblings like schedule_draft_plan and create_draft_plan. It explicitly states the library plan is preserved.

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 implies this tool removes calendar copies while keeping the library plan, but it does not explicitly state when to use it versus alternatives (e.g., full deletion) or provide any prerequisites or conditions.

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