Icu Delete Event

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

Annotations already flag destructive/idempotent, but the description adds substantial context beyond them: the safe-mode gate, that past events are silently skipped rather than errored, the shape of the response envelope, and the env var needed to override. That is exactly the behavioral detail an agent needs before committing an irreversible action.

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 destructive warning and the ONE-scope constraint are front-loaded in the first sentence, and the safe-mode caveat follows immediately. Every sentence carries actionable information, with no padding.

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 two-parameter destructive mutation with full schema coverage and an output schema, the description covers the reset risk, the default mode, refusal behavior, and the response envelope. There is nothing an agent needs before calling it that is missing.

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 coverage is 100%, so both event_id and athlete_id are already documented in the schema. The description mentions deletion by ID but adds no extra semantics about athlete_id scoping or formatting, so the baseline 3 applies.

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 opens with a precise verb and resource ('Permanently delete ONE calendar event by ID') and capitalizes ONE, which implicitly contrasts with the sibling icu_bulk_delete_events. The agent can tell exactly what is affected and how much.

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 gives clear operational context: safe mode is the default, past events are refused, and a hint points to INTERVALS_ICU_DELETE_MODE=full. What it lacks is an explicit pointer to the bulk alternative (icu_bulk_delete_events) or preconditions for the athlete_id override, so a 4 rather than a 5.

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