sonarr_run_command

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

The description explicitly warns 'WRITE: this modifies your Sonarr instance', which adds a clear behavioral warning beyond the annotation readOnlyHint=false. This gives the agent important context about side effects, even though the annotation already implies a non-read-only operation.

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 purpose, and packed with essential details (operation + parameter format + side-effect warning). No filler or redundancy.

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 output schema exists and the tool is a generic command runner, the description covers the essential aspects: what it does, how to specify commands, and its side effects. It could mention available command names more exhaustively, but the examples and schema are adequate for invoking this 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 schema provides only an empty 'body' object with no description, so the description carries the full burden. It explains that the body is a CommandResource with a 'name' and provides examples, adding meaningful guidance for constructing valid commands beyond what the schema offers.

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 a specific verb 'Run' and resource 'Sonarr command', and even provides concrete example command names (RefreshSeries, SeriesSearch, DownloadedEpisodesScan), making it clear this tool executes commands rather than listing or deleting them. This distinguishes it well from sibling tools like sonarr_list_command or 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 description implies usage by stating 'Run a Sonarr command' and giving examples, but it does not explicitly explain when to prefer this tool over alternatives or provide exclusions. No alternative tools are mentioned.

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