sonarr_update_indexer_bulk

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

The description explicitly states 'WRITE: this modifies your Sonarr instance,' which adds clarity beyond the annotations (readOnlyHint=false, destructiveHint=false). It discloses that the operation has side effects and modifies the instance. However, it does not detail the scope of modification or potential impact.

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 a single sentence with no extraneous wording, making it concise and front-loaded. The warning about modifying the instance is useful. However, it is so brief that it sacrifices essential information.

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 has a free-form body parameter and numerous sibling tools, yet the description provides no context on how to construct the body or when to use this tool versus singular update. The output schema covers return values, but input semantics are severely lacking.

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 a single 'body' parameter with additionalProperties true and no description. The description provides no information about the expected structure of the body, such as an array of indexer definitions or fields to update. With 0% schema description coverage, the description fails to compensate.

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 states 'Update indexer bulk,' indicating a bulk update operation for indexers. The verb 'Update' and resource 'indexer bulk' are present, and the 'bulk' suffix distinguishes it from the sibling tool 'sonarr_update_indexer.' However, it doesn't specify what 'bulk' means or which fields are updated.

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 when-to-use guidance is provided. The description does not mention alternatives like 'sonarr_update_indexer' for singular updates, nor does it explain when bulk updating is appropriate.

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