sonarr_update_config_ui

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

Annotations already indicate readOnlyHint=false and destructiveHint=false. The description adds 'this modifies your Sonarr instance,' which reinforces the write nature but does not disclose additional behavioral contexts such as required permissions, side effects, or reversibility. It adds marginal value beyond the annotation.

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, front-loaded with the core action and a clear write indication. Every sentence serves a purpose with no redundancy or fluff.

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 description covers the basic purpose but leaves critical gaps: no parameter semantics, no indication of what the id should be, and no guidance on constructing the body object. The presence of an output schema helps return understanding, but the input side is insufficiently specified for an agent to invoke the tool correctly.

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 offers no explanation of the 'id' or 'body' parameters. With body having additionalProperties true, the agent has no idea what keys are valid or what the id refers to, making correct invocation difficult.

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 'Update UI config' with a specific verb and resource, and the 'WRITE' prefix emphasizes the mutating nature. This distinguishes it from read-only sibling tools like sonarr_get_config_ui and other config update tools.

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 implies usage via the purpose ('Update UI config'), but provides no explicit guidance on when to use it versus alternatives. The 'WRITE' warning is more of a safety note than a usage guideline. No alternatives are named or excluded.

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