prowlarr_bulk_delete_applications

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

The annotation destructiveHint=true already discloses the destructive nature, and the description's 'Bulk-delete' aligns. However, the description adds no extra behavioral context (e.g., permanence, side effects, required permissions) beyond what the annotation provides, so it meets the baseline but does not enrich it.

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, front-loaded with the action, and contains no filler. 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 tool is simple (bulk delete), and an output schema exists so return values need not be described. However, the description leaves the body's exact structure underspecified; given the schema provides no field details and coverage is 0%, an agent might struggle to construct a valid request. It meets the minimum but has clear gaps.

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%, so the description must compensate. It does add that 'body is an ApplicationBulkResource with ids', giving the parameter a type and a key field, but it does not explain the structure of that resource or any other properties. This is partially helpful but not comprehensive.

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 target resource ('applications'), using a specific verb that distinguishes it from the single-delete sibling (prowlarr_delete_application) and the bulk-update sibling (prowlarr_bulk_update_applications).

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 usage context is implied by the word 'bulk' — it is for deleting multiple applications at once — but there is no explicit mention of when to choose this tool over alternatives like the single delete, nor any exclusions or prerequisites. This is adequate but not explicit.

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