list_service_radarr

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description need not reassert safety. It adds the 'non-sensitive' qualifier and the exact GET path, which is useful, but it does not mention auth requirements, pagination, or what data is omitted as sensitive.

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 concise: two short lines, front-loaded with the key purpose, and no filler content. The endpoint line provides useful reference information without bloating the description.

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?

For a zero-parameter, read-only list operation with an output schema and safety annotations, the description supplies enough context: what it returns at a high level ('non-sensitive Radarr server list') and the endpoint. It could be richer about which Radarr servers are included, but the output schema covers return shape and details.

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 zero parameters, and the schema is trivially complete with 100% description coverage. Per the rubric, zero parameters establish a baseline of 4, and the description cannot add meaningful parameter semantics where none exist.

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 a specific verb ('Get') and resource ('Radarr server list'), and the 'non-sensitive' qualifier hints at a distinction from sensitive/settings endpoints. It is clear but does not explicitly differentiate from sibling tools such as list_settings_radarr or get_service_radarr_by_radarr_id.

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?

There is no guidance about when to use this tool instead of alternatives like list_settings_radarr, list_service_sonarr, or get_service_radarr_by_radarr_id. The endpoint line is informational but does not explain selection criteria or context.

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