dashbrr_get_sonarr_queue

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

The description adds useful behavioral context beyond the readOnlyHint annotation by noting that records are paged and that instance_id must be type-prefixed (e.g., 'sonarr-1'). These details help the agent understand data traversal and parameter formatting, which the annotation does not cover.

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 two concise sentences that front-load the primary purpose and immediately state the essential parameter requirement. Every word adds value, with no unnecessary elaboration.

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 the tool's simplicity (one parameter), the presence of an output schema, and the readOnlyHint annotation, the description is nearly complete. It covers the tool's purpose, pagination behavior, and parameter format. It lacks details on pagination mechanics (e.g., page size, navigation), but the output schema likely covers response structure, so this is not a significant gap.

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 a schema description coverage of 0%, the description compensates by explaining the required instance_id format: 'must be type-prefixed, e.g. sonarr-1'. This adds critical meaning beyond the schema's mere 'string' type, clarifying that the instance identifier is not arbitrary.

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 'Sonarr download queue (paged records with series/episode info)' clearly indicates the tool retrieves the Sonarr download queue, distinguishing it from sibling tools for other services (Radarr, Lidarr, etc.) and from Sonarr stats. Although it lacks an explicit verb like 'get' or 'list', the noun phrase combined with the tool name makes the purpose unambiguous.

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 when the Sonarr download queue is needed, but does not explicitly state when to use this tool over alternatives like dashbrr_get_sonarr_stats or the queue getters for other services. No exclusions or alternative recommendations are provided, leaving the agent to infer from sibling names.

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