prowlarr_bulk_delete_download_clients

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

The description adds no behavioral context beyond the destructiveHint annotation. It does not warn about irreversibility, confirmation requirements, or side effects. Since the annotation already flags destructiveness, the description adds no new information.

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?

Two sentences with no filler. The main purpose is front-loaded, and the body type is mentioned succinctly. 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?

The description is too sparse for a destructive bulk operation with a nested body parameter. It doesn't explain how to specify which clients to delete, what the response contains (though output schema exists), or any prerequisites. The agent is left guessing about the resource structure.

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 0% for the 'body' parameter. The description says 'body is a DownloadClientBulkResource', which gives a type name but no explanation of required fields (e.g., ids of clients to delete). This is insufficient for an agent to construct the request body.

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 uses the specific verb 'Bulk-delete' and names the resource 'download clients', clearly distinguishing this from single-delete (prowlarr_delete_download_client) and bulk-update (prowlarr_bulk_update_download_clients). It is specific and 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?

The description indicates the tool is for bulk deletion, but provides no explicit guidance on when to choose this over single delete or when not to use it. The usage is implied by the name and 'Bulk-delete' verb, but no alternatives or exclusions are mentioned.

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