radarr_create_importlist

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

Annotations already show readOnlyHint=false and destructiveHint=false. The description adds 'WRITE: this modifies your Radarr instance,' which reinforces the mutating nature but adds little beyond what annotations imply. No additional side effects or idempotency details are provided.

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 two short sentences with no filler. Every word contributes either the core action or a warning, making it highly concise and well-structured.

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 create operation with a free-form body parameter, the description is far too incomplete for correct invocation. It omits body field requirements, relationship to schema endpoints, and any operational context. The output schema exists but cannot compensate for the undefined input contract.

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% and the description provides no information about 'body' or 'force_save'. The 'body' parameter is an open object with additionalProperties true, leaving the agent completely uninformed about required fields or valid structure.

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 'Create import lists' with a specific verb and resource. This distinguishes it from sibling tools like radarr_list_importlist, radarr_update_importlist, and radarr_delete_importlist.

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 on when to use this tool versus alternatives. It does not mention prerequisites, the need to fetch schema first, or that updating existing lists should use a different tool.

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