radarr_get_importlist

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

The readOnlyHint annotation already covers the safe read behavior, and the description's 'Fetch' verb is consistent with that. The description does not add additional behavioral context like error responses, authentication needs, or pagination, but for a simple get-by-id endpoint this is acceptable.

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 sentence with no unnecessary words. It is front-loaded with the action and resource. The minor grammatical issue ('lists' vs 'list') does not detract from clarity.

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 is simple: one required parameter, an output schema, and a readOnly annotation. The description covers the essential usage. It does not mention potential 404 or id source, but these are not critical for a straightforward fetch operation.

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%, so the description must compensate. The phrase 'by id' clarifies that the parameter is the identifier of the import list, but it does not explain where the id comes from or any constraints beyond the schema's integer type. This is minimal compensation for a 0% coverage schema.

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 'Fetch a single import lists by id' clearly specifies the action (fetch), the resource (import list), and the scope (single by id). It effectively distinguishes itself from sibling radarr_list_importlist, which lists all import lists.

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 when you have a specific import list id, but provides no explicit guidance on when to use this alternative tool or when not to. It does not mention radarr_list_importlist as the alternative for listing all import lists.

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