search_series

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

With no annotations provided, the description carries the full behavioral disclosure burden. It reveals that the operation is an 'automatic search' and scopes it to missing monitored episodes, but it does not disclose side effects, asynchronous queuing behavior, permissions, or whether it returns a command resource.

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, front-loaded sentence with no filler or redundancy. Every word adds relevant context about the action and scope.

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 one-parameter tool, the description states the core behavior clearly and the schema documents the only input. However, there is no mention of return behavior, asynchronous execution, or side effects, and the lack of annotations leaves meaningful gaps an agent would need to infer.

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?

The input schema already fully documents the single parameter series_id with 'Sonarr series id', so schema coverage is 100%. The description adds no additional parameter-level meaning beyond the schema, meeting but not exceeding the baseline.

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 names a specific action ('start an automatic search') and a clear resource scope ('all monitored missing episodes of a series'). It is clear enough to distinguish this from episode- or season-level search tools, though it does not explicitly name sibling alternatives.

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 it: when you want to trigger a series-wide search for missing monitored episodes. However, it provides no explicit guidance about when not to use it or how it relates to similar tools like search_season, search_episodes, or run_command.

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