Sonarr: Search Missing Episodes

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

Discloses the async nature of the operation and that the actual search runs in the background. Describes the return value (CommandResource with id and status). Does not contradict annotations (idempotentHint=true is consistent with triggering a potentially idempotent search). No additional side effects or limits are mentioned, but given the simple nature, it's adequate.

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?

Description is two concise sentences with no superfluous words. Front-loaded with the main action, followed by async details and follow-up instructions. Efficient use of space.

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?

Given the tool's simplicity (no input parameters, no output schema), the description provides all necessary context: what it does, async behavior, return value, and how to monitor progress. It is complete for an agent to select and invoke correctly.

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 tool has no parameters, so schema coverage is 100%. The description does not need to add parameter meaning. Baseline for 0 parameters is 4, and the description does not detract.

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 explicitly states the tool triggers a search for all monitored missing episodes. It uses specific verbs ('Trigger Sonarr to search') and resource ('all monitored, missing episodes'), clearly distinguishing it from sibling tools like sonarr_search_episode and sonarr_search_season.

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?

Provides clear guidance on usage: it is an async operation that returns a CommandResource, and instructs to poll status with sonarr_get_command using the returned id. It does not explicitly state when not to use it or mention alternatives, but the context is sufficient.

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