seerr_get_service_radarr

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

The readOnlyHint annotation already indicates a safe read operation, and the description's 'Get' verb is consistent. However, the description adds no additional behavioral context, such as what happens if the radarr_id is invalid, or any caching or performance implications. It neither contradicts nor significantly enriches 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 a single, concise sentence that directly states the tool's purpose. It contains no redundant information and is appropriately front-loaded.

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?

Given the tool's simplicity (one parameter, output schema present), the description covers the core functionality but lacks usage context. It does not address how to obtain radarr_id, when to prefer this over seerr_get_settings_radarr_profiles, or any other operational considerations, making it only minimally complete.

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 input schema has one parameter, radarr_id, with no description, and the tool description does not explain it. Schema coverage is 0%, so the description should compensate, but it does not mention how to obtain the value or what it represents. The parameter is somewhat self-evident as an ID, but the lack of guidance is a notable 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 clearly states the tool's function: it retrieves Radarr server quality profiles and root folders. The verb 'Get' specifies the action, and the resource is explicit. However, it does not differentiate from the sibling tool seerr_get_settings_radarr_profiles, which also deals with profiles, though the name implies broader scope.

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 like seerr_get_settings_radarr_profiles or seerr_list_service_radarr. It does not mention prerequisites, such as needing a valid radarr_id from a prior list call.

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