sonarr_reorder_delayprofile

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

Annotations already indicate this is a write operation (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds 'WRITE: this modifies your Sonarr instance', which is redundant with the annotations and provides no additional behavioral context such as side effects or ordering semantics.

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 (7 words), which is concise, but it is under-specified. It provides no useful structure or content beyond restating the tool name, making it ineffective rather than appropriately concise.

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, the tool is part of a family of delayprofile operations, and the description fails to explain the reordering semantics, parameter meanings, or any prerequisites. The tool is not adequately contextualized for an AI agent to use it correctly.

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?

With 0% schema description coverage, the description must compensate but does not. It does not explain what 'id' refers to or what 'after' means (e.g., the ID of the profile that should follow). The parameters are completely undocumented in the description.

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 'Update delayprofile reorder' is essentially a tautology that restates the tool name without explaining what 'reorder' means. It fails to clarify that this tool changes the priority/order of delay profiles, and does not distinguish it from the sibling 'update_delayprofile' tool.

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 other delayprofile operations like 'update_delayprofile' or 'delete_delayprofile'. The WRITE warning is a safety label, not usage context.

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