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

The description states the tool deletes items, which is a destructive operation, but the annotations declare destructiveHint: false, creating a direct contradiction. Additionally, the description provides no extra behavioral context (e.g., permanence, permission requirements) beyond the delete action itself, and annotations are insufficient to clarify safety.

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 description is two short, focused sentences: one for the primary purpose and one for bulk support. No redundant wording or unnecessary detail, making it highly efficient and easy to parse.

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 tool's simplicity (3 params, 1 required, no output schema), the description covers the essentials but misses the account parameter and fails to address the contradiction with destructive annotations or any side effects. It is adequate for an agent but not fully complete due to these gaps.

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 0%, so the description carries the burden. It explains history_item_id as the ID to delete by and history_item_ids for bulk execution, which adds meaning. However, it omits the 'account' parameter and offers no guidance on formatting or relationships between parameters, leaving partial compensation.

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 the tool deletes a history item by ID, and explicitly mentions bulk execution via history_item_ids, which distinguishes it from sibling delete tools like elevenlabs_delete_audio_isolation_history_item. It is not a tautology and provides specific resource and action.

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 implies when to use (when you have a history item ID to delete) but does not explicitly contrast with alternatives, such as noting that for audio isolation history one should use a different tool. It offers no exclusionary guidance or context beyond the core operation.

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