sonarr_search_missing

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

No annotations are provided, so the description carries the full burden. While it indicates a trigger action, it does not disclose potential side effects, whether the operation is synchronous or asynchronous, or any requirements (e.g., series being monitored). This is a notable gap for an action that could trigger background tasks.

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 one concise sentence that is front-loaded with the action and target. No unnecessary words, and it 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?

For a simple tool with one parameter and no output schema, the description is reasonably complete. It clearly specifies the action and scope (all missing episodes in a series). However, it could be slightly enhanced by mentioning that it triggers a command, but overall it is sufficient.

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 single parameter seriesId is fully described in the schema with a reference to sonarr_get_series. The description adds no additional parameter semantics, but schema coverage is 100%, so a baseline of 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 ('Trigger a search') and the target ('all missing episodes in a series'). It distinguishes the tool from siblings like sonarr_search_episode (single episode) and sonarr_get_wanted_missing (listing, not triggering).

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 provides a clear use case: when you want to initiate a search for all missing episodes of a series. It does not explicitly mention alternatives or exclusions, but the context is clear enough for an agent to choose this over related search tools.

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