delete_movies

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

With no annotations, the description carries the burden of behavioral disclosure. It explicitly states that files are kept unless delete_files is set, which is a useful consequence for an agent to know before invoking. It does not mention reversibility, import-exclusion effects, or payload/response behavior, but the core default behavior is covered.

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?

One front-loaded sentence communicates the primary purpose and the most important behavioral caveat with no filler. Every word earns its place.

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 straightforward batch deletion with three well-described parameters, the description plus schema are enough to use the tool. It lacks an explicit note about return values or error cases, but since there is no output schema and the invocation contract is simple, this is a minor gap.

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 all three parameters. The description adds a small amount of context by linking delete_files to file retention, but it does not materially expand on movie_ids or add_import_exclusion 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 names a specific action ('Remove several movies') and resource ('from the library'), and the plural 'several' combined with 'in one call' distinguishes it from the singular delete_movie sibling. It does not explicitly name the alternative, so it doesn't hit the strongest level of differentiation.

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 wording implies this is for batch removal, leaving single-movie deletion to delete_movie, and file-only deletion to delete_movie_files. However, there is no explicit when-to-use or when-not-to-use guidance, no mention of prerequisites, and no named alternatives.

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