sonarr_search_releases

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

No annotations are provided, so the description carries the full burden. It discloses the default indexer behavior and the fallback instruction, which adds value beyond a simple 'search' statement. However, it does not mention whether the operation is read-only, rate limits, authentication needs, or what happens if the user does not respond.

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, front-loaded with the purpose, and includes the key behavioral detail without any wasted words. Every 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?

Given no output schema and moderate complexity, the description covers purpose, default behavior, and fallback. However, it lacks details on what the tool returns, how to handle multiple alternatives, or what to do if the user does not respond. It is adequate but not exhaustive.

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 description coverage is 100%, so baseline is 3. The description adds meaningful semantics by explaining the default indexer selection and the fallback procedure, which goes beyond the schema's description of the indexer parameter. This helps the agent understand how to use the parameter correctly.

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 verb 'search' and the resource 'available releases for one or more episodes in Sonarr'. It is specific and distinguishes from siblings like radarr_search_releases (different media) and sonarr_lookup (lookup series/episodes).

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 explains the default behavior of using the preferred indexer and the fallback procedure of asking the user for an alternative. This provides clear guidance on when to use the indexer parameter. However, it does not explicitly compare to sibling tools or state when not to use this tool.

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