search_releases

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

With no annotations, the description carries the behavioral disclosure burden. It usefully warns that indexers are queried live and that the call can take a while. It does not disclose whether the operation is read-only, whether it has side effects, or what 'interactive' means in an API context.

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?

Three focused sentences with no filler. The core purpose and return fields are front-loaded, and the latency warning is placed at the end where it supplements rather than obscures the main message.

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 description covers output fields and latency but does not explain which input parameters are actually needed for a valid search, such as requiring series_id or episode_id, nor how detailed and include_rejected affect behavior. With no output schema and no annotations, these are meaningful gaps.

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%, so the baseline is 3. The description adds no input-parameter semantics beyond the schema; the mention of guid and indexerId refers to output values to pass to grab_release, not to this tool's own parameters.

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 and resource: running an interactive indexer search and returning releases with enumerated fields like quality, size, seeders, and custom format score. It also clearly points to grab_release as the downstream consumer of the returned guid and indexerId, which helps differentiate this tool from other search-related siblings.

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 implies usage in a manual/interactive release selection workflow and tells the agent to pass the resulting guid and indexerId to grab_release. However, it does not explicitly contrast this tool with sibling search tools like search_series, search_season, or search_episodes, nor does it state when not to use it.

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