radarr_bulk_update_indexer

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

Annotations already mark readOnlyHint=false, so it is known to be a write. The description adds 'WRITE: this modifies your Radarr instance,' reinforcing the mutating nature. However, it does not disclose specifics like what gets changed, whether all indexers or a subset are affected, or any side effects. No contradiction with 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, immediately stating the action and then flagging it as a write operation. Every word is purposeful, with no filler or redundancy.

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 this is a mutation tool with an untyped 'body' parameter, the description lacks essential contextual information: what request payload is expected, whether it requires specific fields, or how 'bulk' is defined (list vs. all). The output schema exists but does not help with input construction. The description is insufficient for safe and correct invocation.

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 additionalProperties true and no property descriptions (0% schema coverage). The description does not explain the expected structure—e.g., list of indexer IDs, update fields, or how to target indexers—leaving the agent to guess. This is a severe gap for a bulk update tool.

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 'Bulk update indexers' with a specific verb ('update') and resource ('indexers'), distinguishing it from singular radarr_update_indexer and other bulk operations by resource. However, it lacks detail on what 'bulk update' entails or the scope of modifications, so it falls short of a 5.

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 gives no guidance on when to use this tool versus radarr_update_indexer (singular) or radarr_bulk_delete_indexer. It only warns that it's a write operation, which is a behavioral note, not a usage directive. 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.