sonarr_get_command

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

The annotation readOnlyHint=true already indicates a safe read operation, and 'Fetch' is consistent. The description adds the qualifier 'queued/running' which could be a limitation, but it does not disclose additional behaviors like null returns for invalid IDs or any auth requirements. No contradiction with annotations.

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 of nine words, immediately stating the action and target. No filler or repetition, perfectly front-loaded.

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 getter with one parameter, read-only annotation, and an output schema, the description is mostly sufficient. It accurately states what the tool does. Slight deduction for not mentioning how to get the id or listing list_command as a source, but the sibling context partially compensates.

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 description coverage is 0%, so the description must compensate. It mentions 'by id', clarifying that the required 'id' parameter is the command ID. However, it does not explain where to obtain the ID or provide format details, which is a minor gap for a single-parameter tool.

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 'Fetch' and identifies the resource as 'a single queued/running commands' with the qualifier 'by id'. This clearly distinguishes it from sibling tools like sonarr_list_command (list all) and sonarr_delete_command.

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 phrase 'by id' implies this tool is used when you already have a command ID, but the description does not explicitly mention alternatives or when to use this vs list_command. No exclusions or prerequicites are stated, making the guidance mostly implied.

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