radarr_get_config_ui

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

The readOnlyHint annotation is true and the description is consistent with a read-only listing operation. However, the description adds no behavioral context beyond what the annotation already conveys, such as what is returned, whether authentication is needed, or any side effects. With no added context, transparency is limited.

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, but this is under-specification rather than effective conciseness. 'List ui' is incomplete and does not provide sufficient structure to guide the agent. It reads as a placeholder rather than a deliberate, informative summary.

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?

Despite having an output schema and no parameters, the description fails to clarify what 'ui' refers to, leaving the agent to infer from the tool name. It does not explain the intended use case or output, making it incomplete for a tool that should be straightforward to describe.

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 tool has no parameters, so there is nothing to explain. The baseline of 4 applies since the schema has no parameters to clarify.

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 'List ui' is vague but conveys that the tool lists some UI-related resource. It does not specify that it retrieves the UI configuration settings, nor does it distinguish from sibling tools like radarr_update_config_ui or radarr_get_config_ui_by_id. The purpose is at best a vague directive.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusions, leaving the agent without any decision-making support.

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