search_season

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Start an automatic search' hints at a background trigger but does not state whether it launches an asynchronous command, whether it searches all episodes or only missing ones, whether it is reversible, or what the response looks like. For a state-changing operation, this is a significant gap.

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?

A single 10-word sentence with zero filler, front-loaded with the action and the season scope. It is efficient, though the brevity comes at the cost of behavioral and routing detail that would have been valuable.

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 sits in a cluster of ambiguous search operations (search_series, search_episodes, search_releases) and has no annotations or output schema to compensate. A trigger command like this needs to disclose that it kicks off an asynchronous job and how it differs from the interactive release search, neither of which is addressed.

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?

Schema description coverage is 100%, with both parameters already documented ('Sonarr series id' and 'Season number (0 is specials)'). The description adds only the vague notion of 'one season' without providing format, defaults, or usage semantics beyond what the schema already states, so the baseline of 3 applies.

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') and resource ('automatic search for one season of a series'), making the tool's core function clear. The 'one season' scoping implicitly separates it from search_series and search_episodes, though it never names those siblings explicitly.

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 guidance is given for when to use this tool versus closely related siblings like search_series, search_episodes, or search_releases. There are no conditions, exclusions, or alternative routing hints; the agent must infer the selection logic from the tool name and a generic description.

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