Icu Bulk Delete Events

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description adds meaningful behavioral detail: the operation cannot be undone, and safe mode partitions events into `deleted` and `skipped` based on date. It does not describe failure behavior for invalid IDs, but the partition logic is a substantial disclosure beyond annotations.

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 front-loaded with the purpose and destructive warning, then explains the safe-mode partition and the environment override in two compact sentences. Every sentence adds useful information with no repetition or waste.

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?

With a full input schema, an output schema, and annotations covering safety and idempotency, the description supplies the remaining important context: bulk scope, irreversibility, and safe-mode partitioning. An agent has enough information to call this destructive 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?

Schema description coverage is 100%, so the input schema already explains `event_ids` as a JSON array string and `athlete_id` as an optional coach-managed athlete filter. The description refers only generically to the input list and adds no parameter-level semantics beyond the schema, which is the baseline 3 when schema coverage is complete.

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 a specific verb and resource: delete MANY calendar events in a single batch call. The use of "MANY" and "batch" clearly distinguishes this bulk operation from the single-event sibling icu_delete_event.

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?

It clearly establishes the context for use: bulk deletion of many events in one call, and it explains the default `safe` mode versus `full` mode. It does not explicitly name icu_delete_event as the alternative for single-event deletion, so it falls short of full when/when-not guidance.

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