radarr_bulk_delete_exclusions

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

Annotations already declare destructiveHint=true. The description adds a human-readable warning and specifies the target resource (import list exclusions), but it adds no new context beyond the annotation, such as irreversibility or scope of deletion.

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 short and front-loaded with the purpose, but the second sentence ('DESTRUCTIVE: this deletes data.') is largely redundant with the destructiveHint annotation. It is concise but not every sentence adds unique value.

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's complexity (bulk delete) and the presence of an output schema, the description is insufficient. It does not explain the request body structure, how multiple exclusions are identified, or any response behavior. The annotations cover safety but not operational details.

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 has one parameter ('body') with no description and 0% coverage. The description does not mention the body parameter or explain how to specify which exclusions to delete. With such low schema coverage, the description must compensate but fails to provide any parameter guidance.

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 ('import list exclusions'), which is specific and distinguishes it from single-delete or list siblings. The DESTRUCTIVE warning further emphasizes the purpose.

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 provides no explicit guidance on when to use this tool versus alternatives like radarr_delete_exclusions for single deletions. The word 'bulk' implies multiple items, but there is no direct comparison or exclusions provided.

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