Sonarr: Grab Release

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

Warns 'HIGH RISK', explains server-side lookup and cache dependency, and override behavior. Annotations indicate mutation (readOnlyHint=false) but description adds valuable runtime context. No contradiction.

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?

Three sentences, no fluff, with critical warning first. Each sentence earns its place.

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?

No output schema, but mutation tool adequately covers failure scenario and recovery. For two-param tool with its risks explained, this is complete enough.

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 covers both parameters (100%), and description adds: release must be verbatim from search, guid+indexerId key, other fields ride along. should_override explained as UI mirror. Adds real value beyond schema.

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?

Clear verb 'grab' and resource 'release', with action 'queues a download'. Distinguishes from sibling sonarr_release_search which searches, not grabs.

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?

Explicitly instructs to pass release verbatim from sonarr_release_search, and advises re-running release_search if grab fails. Mentions when to use should_override. Lacks explicit 'when not to use' but context is clear.

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