sonarr_update_config_indexer

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

Annotations already indicate readOnlyHint=false, so the write nature is known. The description's 'WRITE: this modifies your Sonarr instance' adds no new behavioral detail beyond what annotations provide. It doesn't disclose specifics like whether the change is reversible, requires a restart, or affects other settings.

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 at two sentences with no fluff. The 'WRITE: this modifies...' part is somewhat redundant with annotations but does add a human-readable caution. It is concise, though under-specified.

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 complex body parameter that is completely undocumented. There is no mention of available fields, required structure, or the role of the id parameter. Given the tool's position among many config update tools, the description is highly incomplete for safe 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?

Schema description coverage is 0%, and the description does not explain the meaning of 'id' or the expected structure of 'body'. The body parameter is an open-ended object with additionalProperties true, requiring documentation that is entirely absent. This is a critical gap.

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 config' which clearly identifies a write operation on the indexer configuration. It distinguishes from siblings like get_config_indexer and update_config_indexer. However, it doesn't explicitly mention that the id parameter targets a specific config, leaving slight ambiguity.

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 about when to use this tool versus alternatives. There is no mention of prerequisites like fetching the current config first, or exclusions such as avoiding this for bulk updates. The 'WRITE' warning is cautionary but not usage guidance.

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