sonarr_search_episodes

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 does disclose an important side effect that the name 'search' hides — the episode is sent to the download client. It stops short of saying whether this is queued, whether it can be undone, or what happens on failure.

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?

Three short sentences, front-loaded with the purpose and then the side effect, with no filler. Slightly clipped but every sentence carries information.

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 single-parameter tool with no annotations and no output schema, the description covers purpose, the download-client side effect, and the source of IDs. Minor gaps remain around failure behavior and what the call returns, but nothing essential to invoking it correctly is missing.

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?

There is a single parameter with 100% schema description coverage ('Array of episode IDs to search for'), so the schema already does the heavy lifting and baseline 3 applies. The description adds only the provenance of the IDs (sonarr_get_episodes), not format or shape details.

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?

States a specific verb+resource ('Search for specific episodes') and clarifies the real effect ('sends the episode to your download client'), which separates it from the sibling read/listing tools. It doesn't explicitly name sonarr_search_season or sonarr_search_series as alternatives, so sibling differentiation is only partial.

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?

Gives a prerequisite ('Use episodeIds from sonarr_get_episodes'), which is useful routing guidance for obtaining valid input. However it never states when to prefer this over sonarr_search_season or sonarr_search_series_command, so the when-vs-alternatives decision is left implied.

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