BetaSeries: search

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

With no annotations, the description must disclose all behavioral traits. It documents parameter constraints, defaults, and maximums (e.g., limit default and max for shows), and states that search results are returned. However, it omits authentication requirements, rate limits, response structure, and error handling, leaving notable gaps.

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?

The description is lengthy but well-structured, with operations listed and parameters formatted consistently. It is front-loaded with the API purpose and avoids redundancy. The length is justified by the complexity of the three operations and their many filters.

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?

Despite a minimal schema and no output schema, the description thoroughly documents all operations and parameters, including constraints and defaults. It lacks an example call and explicit guidance on when to use the tool versus siblings, but provides enough information for an agent to construct valid requests in most search scenarios.

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?

The input schema only defines 'operation' and a generic 'params' object. All specific parameter names, meanings, types, defaults, and allowed values are provided in the description. Without the description, an agent would have no knowledge of the actual parameters, making it the primary source of parameter semantics.

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 explicitly states 'Call the BetaSeries search API' and lists three operations (get-search-all, get-search-movies, get-search-shows) with clear scopes. This distinguishes the tool from siblings like betaseries_movies or betaseries_shows, which handle specific content types rather than aggregated search.

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 provides clear context for each operation's parameters and filters, implying when to use each sub-operation. However, it does not explicitly state when to use this search tool versus sibling tools for direct lookups, nor does it mention any alternatives or exclusions.

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