dashbrr_get_readarr_queue

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

Annotations already declare readOnlyHint=true, so the description adds value by disclosing that `instance_id` must be type-prefixed (e.g., 'readarr-0'). This is a non-obvious behavioral constraint that helps prevent invocation errors. However, it does not detail the queue content or any other operational behavior, so it falls short of a 5.

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 a single sentence with an inline example, extremely concise and front-loaded. Every word earns its place, and it avoids redundancy with the schema or annotations.

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 get-queue tool with one parameter and an output schema, the description adequately covers the essential information: what the tool returns and how to pass the required parameter. It lacks background on prerequisites (e.g., instance configuration) or selection context, but given the low complexity, this is a minor 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 fully compensates by explaining the required format for the sole parameter `instance_id`. The example 'readarr-0' clarifies the type-prefix requirement, adding meaning that the bare string type in the schema does not convey.

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 'Readarr download queue' clearly indicates this tool retrieves the download queue for Readarr, and the name 'dashbrr_get_readarr_queue' reinforces the get action. It distinguishes among sibling queue tools (sonarr, radarr, lidarr) via the explicit 'Readarr' reference, though the verb is only implied by the name rather than stated in the description.

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 no guidance on when to use this tool versus alternatives like sonarr_queue, radarr_queue, or lidarr_queue. There is no explicit context for selecting this tool based on the target application (e.g., books vs. movies or shows).

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