icu_bulk_delete_events

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

Annotations already set destructiveHint=true, idempotentHint=true. The description adds behavioral context: the safe mode partition (deleted vs skipped) and the env var override. No contradiction with 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?

Description is brief (three sentences) but packed with essential info: purpose, destructiveness, safe mode behavior, and env var. No redundant words.

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?

Given the output schema exists and annotations cover safety, the description adequately explains the core behavior (bulk deletion with safe partitioning). It omits details like rate limits or auth, but those are implicit from annotations and context.

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?

Input schema has 100% coverage with descriptions for both parameters (event_ids as JSON array, athlete_id optional). The description adds no extra parameter-specific meaning beyond what the schema provides.

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 'Delete MANY calendar events in a single batch call', specifying the verb, resource, and scope. It distinguishes from siblings like icu_delete_event and icu_bulk_create_events, as the tool name implies.

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 warns 'Destructive — cannot be undone', and explains the safe vs full delete modes with env var control. While it doesn't explicitly list when not to use, it provides clear context for selecting this tool over alternatives.

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