sonarr_search

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

No annotations are provided, so the description carries the burden. It adds useful behavioral details like the fixed result limit ('top 10 results') and the inclusion of 'tvdbId', but does not disclose other potential response fields, error handling, or rate limits. Given the absence of annotations, this is adequate but 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 short sentences, front-loading the core action and then adding the key output detail. Every word contributes value, with no redundancy or filler.

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 tool with one parameter and no output schema, the description provides essential context: what it does, what it returns (top 10 results with tvdbId), and how it connects to the next step (sonarr_add_series). It is sufficiently complete for an agent to select and invoke it correctly, though a brief note on result format or sorting could make it more complete.

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% (term described as 'Series name to search for'), so the baseline is 3. The description reinforces the parameter's purpose ('by name') but doesn't add meaning beyond the schema. No additional parameter details are provided, so the description is not particularly informative beyond the 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?

The description uses a specific verb ('Search') and resource ('TV series by name'), clearly distinguishing it from sibling tools like sonarr_search_episode or sonarr_search_releases. It also states the output scope ('top 10 results') and the key data returned ('tvdbId'), making the purpose unambiguous.

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 positions this tool as a prerequisite for sonarr_add_series ('needed for sonarr_add_series'), giving clear context on when to use it. It doesn't explicitly mention alternatives or when not to use it, but the linkage to add_series is a strong usage signal.

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