sonarr_bulk_delete_episodefile

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

The description repeats the destructiveHint annotation ('DESTRUCTIVE: this deletes data') but adds no additional behavioral context. Unlike the TDQS example that added date-range scope, this description provides no extra safety or operational context beyond what annotations already convey.

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 brief but not effective; both sentences are redundant with the tool name and annotations. It is under-specified for a destructive bulk operation, and the short length does not compensate for the lack of valuable content.

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 bulk delete with an undocumented request body, the description is severely incomplete. It fails to explain what the body should contain, how files are selected, any safety checks, or what the response indicates. The user receives no actionable 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?

With schema description coverage at 0% and a single 'body' param (object, additionalProperties true), the description carries the full burden of explaining how to specify which episode files to delete. It gives no hints on required fields, structure, or examples, leaving the agent completely unguided.

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 'Delete episodefile bulk' simply restates the tool name without adding specific scope or details. It does not distinguish from the sibling tool 'sonarr_delete_episodefile' beyond the word 'bulk', which is already in the name.

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?

No guidance is provided on when to use this tool versus alternatives like sonarr_delete_episodefile or sonarr_bulk_edit_episodefiles. The description offers no context, prerequisites, or exclusions.

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