Sonarr: Re-grab Queue Item

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

Annotations already declare readOnlyHint=false and destructiveHint=false. The description adds context that it 'forces a re-grab from the indexer' and 'returns the updated queue entry,' but it does not disclose potential side effects (e.g., duplicate downloads) or network impact. With annotations covering basic safety, the description adds moderate value.

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?

Two sentences (20 words) efficiently convey purpose, usage context, and return value. The first sentence is action-oriented, and no unnecessary information is present.

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 tool with one parameter, the description covers purpose, when to use, and return value. No output schema exists, but 'Returns the updated queue entry' is sufficient. The tool is low complexity, so completeness is high.

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 coverage is 100% and the parameter description in the schema is clear ('The Sonarr queue item id (from sonarr_queue)'). The tool description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 uses the specific verb 're-grab' and clearly identifies the resource 'stuck queue item'. It distinguishes from sibling tools like sonarr_queue (list), sonarr_queue_remove (remove), and sonarr_grab_release (grab release) by focusing on re-grabbing stuck items.

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 provides when-to-use context: 'when a download is hung or the file is corrupt.' However, it does not mention when NOT to use it or compare with alternatives like sonarr_queue_remove, so it lacks explicit exclusions or comparisons.

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