search_releases

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

With no annotations provided, the description carries the full burden. It discloses that the tool queries every enabled indexer, that it is interactive, and that it may take a while. It also implies it does not grab releases by pointing to grab_release, though it does not explicitly state side effects or lack thereof.

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 sentences with no filler. The main purpose is front-loaded, followed by an important performance caveat and a pointer to the next step. Every sentence earns its place.

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 explains what the tool returns, how broad the search is, and that it can be slow, which is enough for an agent to select and invoke it. It does not elaborate on what 'interactive' means operationally, but the schema covers the required movie_id and optional params.

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 schema already documents all three parameters. The description adds little parameter-level meaning beyond mentioning 'releases' and 'rejections,' but the schema covers limit and include_rejected adequately.

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 uses a specific verb ('Run an interactive indexer search'), names the resource ('a movie'), and specifies the output ('releases found, with their rejections and custom format scores'). It also differentiates itself from the sibling grab_release by explicitly saying 'Grab one with grab_release.'

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?

It provides clear context: use this tool to search across every enabled indexer, and it can be slow. It also points to grab_release as the follow-up action. It doesn't explicitly list when-not-to-use alternatives, but the search-then-grab flow is well implied.

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