radarr_bulk_create_exclusions

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

The description repeats the annotation-inferred write behavior ('WRITE: this modifies your Radarr instance') without adding new operational detail such as permission requirements, duplicate handling, or response behavior. Given readOnlyHint=false is already present, this adds no new value.

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 brief and front-loads the purpose in the first sentence. The second sentence is somewhat redundant given the annotations, but generally efficient and well-structured.

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?

While the high-level purpose is clear, the tool's input is an opaque body array with no item definition. The description does not mention the format of entries, any limits, or preconditions, making it insufficient for correct invocation despite an output schema being present.

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 has a single 'body' array with empty item schema, and the description provides no details about the required structure of exclusion objects. At 0% schema coverage, the description fails to compensate, leaving the agent without necessary parameter semantics.

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 tool creates multiple import list exclusions, using a specific verb and resource. However, it does not explicitly distinguish from the sibling radarr_create_exclusions, relying on the 'bulk' in the name and the word 'multiple'.

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 tool versus alternatives like radarr_create_exclusions or radarr_delete_exclusions. The only context is a write warning, which conveys the mutation nature but not selection criteria.

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