sonarr_get_queue

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

With no annotations, the description carries the burden. It discloses that this is a read-only operation via 'Get' and 'Shows', but offers no detail on queue semantics (e.g., whether paused items are included) or response format. It is not misleading but adds limited behavioral context beyond the obvious.

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, front-loaded with the core purpose, and no wasted words. Every phrase adds value (current, active, progress).

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 read tool with one optional parameter and no output schema, the description is adequate. It states what it returns (downloads and progress) and the context (current queue). It could mention whether the queue includes queued items, but that is a minor gap for an AI agent selecting the 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 only parameter, 'limit', already has a clear description in the schema (max items, default 10). The tool description adds no additional parameter meaning, so baseline 3 applies due to 100% schema coverage.

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 states a specific verb ('Get') and resource ('current Sonarr download queue'), and clarifies it shows active downloads with progress. This clearly distinguishes it from siblings like sonarr_get_history (past items) and sonarr_remove_from_queue (mutation).

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 clear context that this is for viewing current queue status, which implies when to use it. It does not explicitly mention alternatives or exclusions, but the 'current' and 'download queue' wording makes the appropriate scenario obvious.

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