sonarr_search_episode

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

With no annotations, the description carries the full burden of behavioral disclosure. It says 'Trigger a download search' but does not explain that this may initiate automatic downloads, add items to the queue, or what the command response looks like. This ambiguity is a significant gap for an action that could have side effects.

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 sentence, concise and front-loaded with the verb 'Trigger.' Every word earns its place, with no redundant or vague phrasing.

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?

The tool is simple with one parameter and no output schema, but the description is extremely sparse. It does not explain the expected outcome (e.g., initiates a search that may download releases), whether the operation is asynchronous, or what happens after triggering. This leaves the agent without enough context to predict the tool's behavior.

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 schema description for episodeIds ('Episode ID(s) (from sonarr_get_episodes)') provides clear meaning and source for the parameter. Since schema coverage is 100%, the description adds no extra parameter context, aligning with the baseline score of 3.

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 states a specific action: 'Trigger a download search for specific episode(s).' It clearly identifies the verb, resource, and target. However, it does not explicitly distinguish itself from sibling tools like sonarr_search or sonarr_search_missing, which also involve searching.

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?

No when-to-use or alternative guidance is provided. The description does not mention that this tool is for triggering searches for known episode IDs, nor does it differentiate when to use sonarr_search_missing for missing episodes or sonarr_search_releases for release searching.

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