Sonarr: Search Season

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

The description adds value beyond annotations by revealing the async nature and the returned CommandResource, instructing polling behavior. Annotations already indicate idempotence and non-read-only, but the description fills in the async detail, which is crucial for correct use.

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 two sentences, front-loading the action in the first sentence and providing critical async workflow in the second. Every word contributes value with no redundancy.

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 (2 parameters, no nested objects), the description sufficiently covers purpose, behavior, and follow-up steps. The lack of output schema is mitigated by describing the return type and polling mechanism.

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 provides 100% coverage with descriptions for both parameters (series_id and season_number). The description does not add additional semantic context beyond the schema, so it meets the baseline without enhancement.

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 tool triggers a search for 'one season of one series', distinguishing it from sibling tools like sonarr_search_episode (single episode) and sonarr_search_series (whole series). The verb 'search' and resource 'season' are specific and unambiguous.

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 explicitly advises to poll status with 'sonarr_get_command' using the returned ID, providing a clear post-invocation workflow. However, it does not explicitly state when not to use this tool or compare it to alternatives like sonarr_search_missing, which limits guidance slightly.

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