sonarr_bulk_delete_customformat

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

The description says 'DESTRUCTIVE: this deletes data,' but this simply restates the destructiveHint annotation. It adds no additional context about what data is affected, whether it is irreversible, or any other behavioral implications. The annotation already covers the destructive nature, so no value is added.

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 very short, but it uses one of its two sentences to repeat the destructive annotation, which is redundant. The remaining sentence is clear but doesn't earn its place by adding depth; still, it is not verbose.

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 is a bulk deletion operation with a generic, undocumented 'body' parameter, the description is severely incomplete. It does not specify the payload structure, how multiple items are identified, or any additional behavioral notes. The existence of an output schema does not 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 input schema contains one optional 'body' parameter with no description and 0% schema description coverage. The description does not explain what the body should contain (e.g., list of IDs), leaving the agent entirely without guidance for constructing a valid request.

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 customformat bulk' with a specific resource (customformat) and mode (bulk). It distinguishes from the singular 'sonarr_delete_customformat' sibling by the 'bulk' modifier. Though grammatically awkward, the meaning is unambiguous.

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 bulk delete versus the singular delete or how to structure the request. It does not mention any prerequisites or alternatives, so the agent cannot determine appropriate use cases.

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