radarr_reorder_delayprofile

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

The description adds 'WRITE: this modifies your Radarr instance,' which explicitly discloses side effects beyond the readOnlyHint=false annotation. It also explains that reordering is relative to 'another entry.' This adds useful context without contradicting annotations.

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, with two short, front-loaded sentences. It states the purpose, key parameter, and write warning with no filler or redundancy.

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 simple two-parameter operation with an output schema, the description is minimally adequate but lacks details on prerequisites, behavior when 'after' is omitted, and any side effects on ordering. It could benefit from a brief example or clarification of expected behavior.

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. It only names 'after' as a query parameter but does not explain its value type or semantics (e.g., ID of the entry to move after). It does not clarify that 'id' is the target delay profile ID, leaving the parameter meanings ambiguous.

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 action ('Reorder delay profiles after another entry') with a specific verb and resource. It distinguishes this from sibling tools like create/update/delete delayprofile by focusing on reordering.

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 for reordering delay profiles relative to another entry, but it does not explicitly state when to prefer this over alternatives (e.g., update_delayprofile) or provide exclusions. The context is clear enough for basic use, but no explicit guidance is given.

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