delete_moviefile_bulk

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

The description adds no behavioral context beyond what annotations already declare. Annotations include destructiveHint=true and idempotentHint=true, and the description simply restates 'Delete MovieFile' without explaining effects, permanence, or prerequisites. No additional transparency is provided.

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 concise and front-loaded with the action and endpoint. The note about reading the schema is useful and placed at the end, keeping the main purpose clear. No wasted words.

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 bulk delete operation, the description is incomplete. It doesn't explain what the body should contain, how the deletion works, or any constraints. The pointer to the schema is insufficient because the schema itself is generic and uninformative. The presence of an output schema doesn't compensate for the missing input guidance.

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?

The description instructs the agent to 'Read the matching GET or the /schema endpoint first to see the fields this resource expects', which gives a pointer but no direct information about the body structure. Since the schema itself is an open object with additionalProperties=true and 0% coverage, the description provides some guidance but doesn't explain what the payload should contain (e.g., a list of IDs).

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 states the action 'Delete MovieFile' and includes the HTTP method and path 'DELETE /api/v3/moviefile/bulk', which clearly indicates a bulk deletion operation. It distinguishes from single-delete tools through the 'bulk' in the URL, though it doesn't explicitly contrast with siblings like delete_moviefile_by_id.

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 guidance on when to use this tool versus alternatives. It doesn't mention that it's for deleting multiple movie files, nor does it contrast with single-delete or editor tools. The agent must infer usage from the tool name and URL.

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