Sonarr: Release Search

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

The description adds value beyond annotations by disclosing that the tool 'hits every enabled indexer in real time — slow and rate-limit-sensitive' and clarifies it does not grab. Annotations readOnlyHint and openWorldHint are consistent and non-contradictory.

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 three sentences, each serving a clear purpose: stating the action, providing usage guidance, and detailing parameter options. No extraneous words.

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 complexity, the description covers purpose, behavior, usage context, parameter guidance, and future integration with sonarr_grab_release. No output schema exists, but the description implies the return type ('candidate ReleaseResource entries'), which is sufficient.

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 coverage is 100%, and the description adds meaning by explaining parameter relationships (e.g., season_number used with series_id, series_id required unless episode_id set). This helps the agent understand optionality and scope.

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 clearly states the tool performs a live indexer search for releases and returns candidate entries without grabbing. It specifies the verb, resource, and return type, and distinguishes from sibling tools like sonarr_grab_release.

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 explicitly says 'call only when the user wants to pick a release manually' and mentions it is slow and rate-limit-sensitive, providing clear when-to-use guidance. It also explains the three scoping options and that at least one is required.

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