sonarr_queue

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

No annotations provided, so description carries full burden. It details behavioral traits: surfaces trackedDownloadStatus/State and statusMessages/errorMessage, and groups items by downloadId. This goes beyond a simple listing, providing insight into output structure and grouping.

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, efficiently front-loaded. First sentence states core purpose, second adds diagnostic details and grouping. No filler, every sentence adds value.

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?

Given zero parameters and presence of output schema, description fully covers purpose and key output features: diagnostics for stuck items and grouping by downloadId. Sufficient for an agent to understand tool's value and 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?

No parameters in input schema, so baseline is 4. Description adds no parameter info, but schema coverage is 100% and there are no parameters to explain.

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?

Description clearly states 'Show current download queue in Sonarr, with diagnostics for stuck items.' This specifies the verb 'show', resource 'download queue', and special feature of diagnostics, distinguishing it from sibling tools like sonarr_delete_queue_item.

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?

Usage is implied for checking queue status, especially stuck items, but no explicit guidance on when not to use or alternatives (e.g., sonarr_history for historical data). The description lacks explicit when-to-use or when-not-to-use context.

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