sonarr_update_indexer

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

Annotations already declare readOnlyHint=false, and the description reinforces this with 'WRITE: this modifies your Sonarr instance.' While this aligns with the annotations, it adds little beyond the annotation: it does not describe what specifically is modified, whether changes are reversible, or any side effects. With annotations present, the description offers minimal additional behavioral insight.

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 extremely short—one sentence plus a warning—but under-specification is not equivalent to conciseness. The words 'Update indexers' largely restate the tool name, and the WRITE warning adds only a generic note already covered by annotations. It lacks structured, essential details while being minimal in length.

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?

This is a 3-parameter tool with a nested body object, no parameter descriptions, no usage guidance, and a sibling tool for bulk updates. The description is far too sparse to help an agent select and invoke the tool correctly. It fails to mention required fields, the purpose of 'body', how 'force_save' behaves, or any distinction from 'update_indexer_bulk'.

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% and the description provides no parameter information. The schema defines 'id', 'body', and 'force_save' with no descriptions, and the description does not compensate by explaining their meanings or expected formats. This leaves all parameters semantically opaque.

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 indexers' with a specific verb and resource, making the primary action clear. However, it does not distinguish this tool from the sibling tool 'sonarr_update_indexer_bulk' (plural vs. singular update), and 'indexers' is plural while the schema expects a single 'id'. This ambiguity reduces clarity.

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. There is no mention of whether it should be used for a single indexer update, when to prefer bulk updates, or any exclusions. The description is purely declarative with no contextual usage information.

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