sonarr_search_series_command

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

No annotations are provided, so the description carries the full behavioral burden and largely fails to. It does not reveal that this issues a command (likely queued/async), whether it hits indexers, whether it can trigger downloads, or what permissions/state it requires.

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?

Two short sentences, front-loaded with the operation and followed by the UI analogy; no filler. Slightly redundant but efficient.

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 command-type tool with no annotations and no output schema, the description should at minimum explain that it dispatches a search job and what the caller gets back. That behavior is entirely absent, so an agent cannot predict the result of the call.

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% with a single documented param (seriesId as 'Sonarr series ID'), so the schema already carries the semantics. The description adds no extra meaning about the parameter, which is acceptable under the baseline rule.

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 (search) and resource (all monitored episodes of a series) and adds scope detail ('monitored') that distinguishes it from an unfiltered search. It does not, however, distinguish itself from the near-identically named sibling sonarr_search_series, leaving the agent to guess at the difference.

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 'Search All button functionality' analogy implies when a user would reach for this tool, but there is no explicit statement of when to use it versus sonarr_search_series, sonarr_search_episodes, or sonarr_search_season. Usage is implied rather than specified.

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