Delete Calendar Item

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

Descriptions explicitly state irreversibility ('cannot be undone'), adding context beyond annotations (destructiveHint). However, annotations already indicate destructive behavior, so the added value is limited but consistent.

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?

Contains some repetition ('This cannot be undone' said twice in similar phrasing). Could be more concise, but the key information is front-loaded in the first sentence.

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 two parameters and no output schema, the description covers purpose, irreversibility, required params, and API endpoint. It is reasonably complete given the tool's simplicity.

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?

Schema covers both parameters fully (100% coverage). Description mentions required parameters and provides endpoint path, adding minimal context beyond the schema. 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?

Clearly states it deletes a single Calendar Item from Schedule (Legacy) records. However, it does not differentiate from other delete tools among the many sibling tools, so it misses explicit sibling differentiation.

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 on when to use this tool versus alternatives like bulk_delete or other delete tools. It states 'Use this to permanently delete' but does not specify conditions or exclusions.

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