delete_episode_files

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly states that files are deleted 'from disk', making the destructive nature clear, but it omits any mention of irreversibility, partial failure behavior, or permission requirements that would be valuable for a destructive operation.

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 a single sentence that front-loads the verb and object with no filler. Every word adds meaning: 'several' conveys batch scope, 'from disk' clarifies the effect, and 'in one call' distinguishes from repeated single deletions.

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 simple tool with one parameter and no output schema, the description covers the core action adequately. However, it lacks explicit guidance on when to choose this over the singular variant, and there is no mention of error handling or return behavior, which would round out the 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 the parameter 'episode_file_ids' already described as 'Episode file ids to delete'. The description adds only the word 'several', which reinforces the array nature, but does not provide additional semantic meaning beyond the schema.

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 action ('Delete'), the resource ('episode files'), the scope ('several'), and the location ('from disk'). It effectively distinguishes this batch operation from the sibling 'delete_episode_file' by emphasizing 'in one call'.

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 phrase 'several... in one call' implies this is for batch deletion of multiple episode files, providing some usage context. However, it does not explicitly mention the singular alternative 'delete_episode_file' or state conditions for when one should be preferred over the other.

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