radarr_update_config_ui

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

The description adds 'WRITE: this modifies your Radarr instance,' which aligns with the annotations (readOnlyHint=false) but does not add new behavioral context. It omits details about side effects, reversibility, or required permissions.

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 very short, but the first sentence is a near-tautology and the second is a generic write warning. It is not front-loaded with useful information, though it is not unnecessarily verbose.

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 handles nested objects and has no schema coverage, yet the description provides no context about the UI configuration resource, what fields are expected, or how the update behaves. This is critically incomplete for an agent to invoke it reliably.

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 0% description coverage, and the description does not compensate. It fails to explain the meaning of 'id' or the structure of 'body', which is a generic object with additionalProperties allowed. An agent has no guidance on what fields to provide.

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 ui' which is a clear verb+resource pairing, matching the tool name and distinguishing it from read-only config tools like radarr_get_config_ui. However, it does not elaborate on what 'ui' settings are or differentiate from other update config tools beyond the resource name.

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 on when to use this tool versus other config update tools or the read counterparts. The 'WRITE' note implies it is for modification, but there is no explicit mention of alternatives or prerequisites.

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