delete_audio_isolation_history_item

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=true, so the safety and repeat-behavior profile is covered structurally. The description adds nothing on top of that — no mention of permanence, authorization requirements, or side effects — so it contributes no behavioral context.

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?

It is a single short sentence with no redundancy or filler, so there is nothing wasteful to trim. However, minimal length here reflects under-specification rather than efficient front-loading, so it earns only an adequate score.

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 destructive, open-world delete operation, the description offers no guidance on irreversibility, error conditions, or what a caller should have in hand before invoking it. With no output schema, the annotations carry most of the useful signal, leaving the description effectively empty of 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?

Schema description coverage is 100% with a single required parameter (history_item_id) that is fully documented in the schema. Since the structured schema does the heavy lifting and the description adds no additional meaning, the baseline of 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 is a verbatim restatement of the tool name and annotation title ('Delete Audio Isolation History Item'), adding no verb-resource scope beyond the identifier itself. It does not distinguish this delete from the many other delete_* siblings such as delete_speech_history_item or delete_dubbing.

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?

There is no when-to-use, when-not-to-use, or alternative routing guidance. An agent must infer from the name alone that this deletes a specific audio isolation history record, with no hint about prerequisites such as first listing history items via get_audio_isolation_history.

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