Delete Media Extended Audio Description

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

Annotations already flag destructive=true, idempotent=false and openWorld=true, so the safety profile is covered. The description adds value beyond them by disclosing side effects ('may share access, notify people or incur provider charges') and restating the confirm gate, which tells the agent this write has external consequences.

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?

Two tight sentences, with the verb+resource front-loaded and the mutation precondition and side effects following. No filler or repetition.

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 no output schema the description need not explain return values, and the annotations carry the safety profile. It covers the identifier, the confirmation gate and the blast radius, which is nearly everything needed to call a destructive delete correctly; only rollback/recovery context is absent.

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 schema already documents id, account and confirm. The description only echoes the hashed-id and confirm semantics without adding format, resolution or side-effect meaning per parameter, 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?

States a specific verb (deletes) and resource (extended audio description) and names the identifier it operates on. It clearly separates itself from generic delete_media, though it does not explicitly differentiate from the closely related get_media_extended_audio_description / order_extended_audio_description siblings.

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?

Supplies one real precondition (confirm=true must be set for the mutation), which is more than nothing. However, it gives no when-to-use / when-not guidance and does not point at the restore or list siblings for recovery or verification.

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