sonarr_search_season

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

Behavior is partially disclosed: confirms that confirm=True triggers action and confirm=False is dry-run. No annotations exist, so description carries full burden; but lacks details on side effects, permissions, or rate limits.

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?

Two short sentences, front-loaded with main action. Efficient but could be slightly more concise. No unnecessary words.

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?

Output schema exists, so return values are covered. But description omits prerequisites (e.g., series must exist) or expected behavior when season is already downloaded. Adequate but not fully complete.

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?

With 0% schema description coverage, description only adds meaning to 'confirm' (dry-run vs launch). No explanation for series_id or season_number beyond their names. Insufficient compensation for missing schema descriptions.

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/download for a whole season. It distinguishes from siblings like sonarr_set_season_monitoring and sonarr_purge_season, but doesn't explicitly differentiate itself.

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 guidance on confirm parameter: set to True to launch search, False for dry-run. This helps the agent decide when to invoke. However, no guidance on when not to use this tool or alternatives.

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