radarr_bulk_delete_customformat

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

Annotations already declare destructiveHint=true; the description adds only a redundant warning ('DESTRUCTIVE: this deletes data') without additional context such as irreversibility, impact on associated items, or required permissions. Thus it provides little beyond the structured annotations.

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 two short sentences and directly states the purpose and the destructive warning. It is appropriately sized without unnecessary 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?

Although the tool is a bulk delete operation, the description fails to specify the request body format, the nature of 'bulk' (e.g., list of IDs), or any prerequisites. The output schema is present but not described. This makes it inadequate for an agent to invoke correctly.

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 schema contains one 'body' parameter with 0% coverage; the description provides no information about the expected body structure (e.g., array of IDs). The additionalProperties:true object leaves the agent without any guidance on how to construct 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 (bulk delete) and the resource (custom formats), using a specific verb. It distinguishes from the sibling radarr_delete_customformat by indicating a bulk operation.

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 description does not explicitly state when to use this tool vs. alternatives. The 'bulk' qualifier implies it is for deleting multiple custom formats, but no direct comparison to radarr_delete_customformat or other bulk operations is provided.

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