sonarr_search_releases

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

With no annotations, the description carries the transparency burden. It discloses that the tool only searches and returns candidates, and implicitly that grabbing is a separate step. However, it omits potential side effects, rate limits, result limits, or pagination behavior. It adds useful detail about return fields but is not exhaustive.

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 two sentences with no wasted words. It front-loads the purpose, then summarizes return content, and ends with a useful next-step pointer. Every sentence contributes.

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 one-parameter tool with no output schema, the description is quite complete: it states what is returned and how to use the result. It doesn't mention sorting, result limits, or error scenarios, but these are less critical for this basic search operation.

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 fully documents the episodeId parameter, including where to obtain it (from sonarr_get_episodes). The description adds no additional parameter-level nuance, so with 100% schema coverage the baseline of 3 is appropriate.

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 an action ('Search indexers') with a specific scope ('for a specific episode') and outcome ('Returns release candidates with quality, size, seeders, and rejection reasons'). This distinguishes it from broader search tools like sonarr_search_all or sonarr_search_missing.

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?

It gives a follow-up instruction to use sonarr_grab_release with guid and indexerId, but does not explain when to choose this tool over sibling search tools (e.g., sonarr_search_episode vs manual release search). No explicit when-not-to-use guidance is provided.

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