Icu Delete Workout Folder

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

Annotations already declare destructive=true, but the description adds context annotations cannot carry: irreversibility, that applied calendar events survive the delete, and that `safe` mode (the default) refuses non-empty folders and reports them in the `skipped` envelope. That is real behavioral disclosure, not restatement, and it does not conflict with the idempotent/openWorld hints.

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?

Front-loaded with the verb and cascade scope, then consequences, then sibling routing, then the safe-mode caveat. Every sentence changes agent behavior; nothing is boilerplate or repeated from the schema.

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?

An output schema exists so return values need no explanation, yet the description still flags the `skipped` envelope an agent must inspect to interpret a partial refusal. For a destructive cascade delete with only two parameters, nothing needed to call it correctly 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% and both parameters are documented in-schema (folder_id sourced from icu_get_workout_library, athlete_id for coach multi-athlete use). The description reinforces the singular 'ONE' constraint on folder_id but adds no new format, range, or lookup semantics beyond the schema, so 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?

States a specific verb ('permanently delete'), the exact resource ('ONE library folder or training plan'), and the cascade scope ('AND every workout in it'). It also names the two sibling operations that handle the narrower cases (icu_delete_workout, icu_delete_event), so an agent can distinguish it from nearby tools without opening a schema.

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?

Explicitly routes alternatives: single library workout -> icu_delete_workout, lingering calendar events -> icu_delete_event. It also states a precondition ('Confirm with the user before calling if unsure') and the default-mode behavior that selects a different outcome, which is exactly the when/when-not guidance the dimension asks for.

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