lookup_series

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly says this searches TVDB, returns candidates rather than a single guaranteed match, and lists the fields returned. For a simple read-only lookup, this provides sufficient transparency; no side effects or destructive behavior are implied.

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 two tight sentences with no filler. It front-loads the core purpose and immediately follows with the return shape and the next action, making every sentence valuable.

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 tool is simple with only one required parameter and no output schema, yet the description covers the input format, the output fields, and the recommended next step. There is nothing essential missing for an agent to invoke this tool correctly.

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 schema already documents the 'term' parameter with 100% coverage, but the description adds meaningful detail by showing the accepted id-prefix formats ('tvdb:121361', 'imdb:tt0944947') and clarifying that either a title or an id term can be used. This goes beyond the schema's single example and helps the agent construct valid input.

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 specific action ('Search TVDB for series to add') and the resource being searched. It also explains the return payload and downstream use, making the tool's purpose unmistakable. It does not explicitly contrast itself with the sibling 'search_series', but the 'to add' context and TVDB/IMDb id support make the distinction inferable.

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 gives clear context: this is the lookup step before adding a series, and it tells the caller to pass the returned tvdbId to add_series. It does not explicitly state when not to use it or name alternative tools, but the intended workflow is clear enough for an agent to choose it correctly.

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