sonarr_search

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

No annotations are provided, so the description must convey behavioral traits. It indicates an external search (TheTVDB) but does not confirm read-only semantics, mention side effects, or discuss prerequisites like authentication or rate limits. The description is neutral and not 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 a single, focused sentence with no wasted words. It could be slightly more informative (e.g., specifying the return type), but its conciseness is effective for a straightforward search tool.

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?

The tool is simple (2 parameters, no output schema), but the description does not clarify what the search returns (e.g., a list of series objects). While the purpose is clear, the lack of output schema places a burden on the description to hint at the response, which it fails to do.

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?

Since schema description coverage is 100% and the existing descriptions ('Search query (series title)', 'Max results to return (default: 200)') are adequate, the tool description adds no additional meaning. Per guidelines, baseline 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 the action ('Search'), the target resource ('TheTVDB'), and the purpose ('for new series to add to Sonarr'). This verb-resource combination distinguishes it from siblings like 'sonarr_get_series' (lists existing series) and 'radarr_search' (searches movies), making the tool's role 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 implies when to use the tool (when searching for new series to add to Sonarr) but offers no explicit guidance on when not to use it or alternatives (e.g., 'sonarr_trigger_search' for episode searches). The purpose is clear but lacks explicit exclusion or comparison to siblings.

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