search_season

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that this kicks off an indexer search rather than a download, but says nothing about whether it is asynchronous, whether results are grabbed automatically, or any rate/queue implications.

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 lines: the action and scope come first, the illustrative example second. No filler and nothing is buried.

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?

An output schema exists, so return values need not be explained. However, for a tool that initiates a multi-episode search, the description omits what happens after the search (queued grabs, async results) and the valid season value domain, leaving gaps an agent would need to guess at.

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 coverage is 50%: 'series' is documented as 'Series ID or title' while 'season' has no description. The example implicitly shows season as a numeric value and series as a title, adding modest meaning, but the accepted season formats (e.g. 0 for specials) remain unclear.

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?

States a specific verb and resource ('Trigger an indexer search for a whole season') and clarifies scope with 'season packs or every episode,' which implicitly separates it from the episode-level sibling. It never names search_episodes explicitly, so sibling differentiation is left to inference.

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 example ('Search season 2 of The Capture') gives a concrete usage context, but there is no explicit when-to-use/when-not guidance and no mention of search_episodes as the alternative for single episodes.

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