radarr_action_importlist

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

The description voluntarily adds 'WRITE: this modifies your Radarr instance,' which is helpful and aligns with readOnlyHint=false. It also notes that 'name selects the action,' but it does not elaborate on what actions exist or what side effects they may have. Given the presence of annotations, this is only a modest contribution beyond the structured metadata.

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 brevity here is under-specification rather than effective conciseness. The phrasing 'Run an action on a action' is awkward and unpolished, and the sentence does not convey essential details in a structured way.

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 numerous siblings, the description leaves the agent entirely in the dark about valid actions, request body shape, and response expectations. It is not sufficient for correct invocation of this action-based tool.

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 description gives minimal meaning to 'name' by stating it selects the action, but it completely ignores the 'body' parameter, which is an object that likely carries action-specific payload. With schema description coverage at 0%, the description fails to compensate for the lack of parameter documentation in the 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 'Run an action on a action' is tautological and grammatically confusing. It does not state what the tool does with respect to import lists, nor does it differentiate from sibling action tools. The only hint is the tool name itself, which the description fails to leverage.

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?

No guidance is given on when to use this tool versus alternatives like radarr_action_indexer or radarr_action_downloadclient. No prerequisites, scenarios, or exclusions are mentioned, leaving the agent without context for selection.

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