search_tvdb

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

Without annotations to lean on, the description carries the burden. It clearly states the operation is a search/read and describes the return value as TVDB IDs. Does not mention rate limits or endpoints, but such details are not necessary for an agent to correctly invoke this tool.

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 sentences, front-loaded with the operation, then the exact trigger scenario, and the follow-up action. No filler and 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 copes for the basic search flow and the follow-along with add_series, and an output schema is present. Gaps from a partially undocumented language parameter and no explicit failure/empty-result behavior, so it is not fully complete without schema inspection.

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 description adds meaning for 'query' by saying 'by name', but the optional 'language' parameter is entirely undocumented and schema description coverage is 0%. The description must compensate at this coverage level but it only does so for one of two 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?

States a specific verb (Search) + resource (TVDB) + input (show name) + output (matching TVDB IDs). Clearly differentiates from the sibling add_series and add_anime tools by focusing on lookup only, not adding.

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?

Explicitly says when to use it: when an anime add fails due to AniDB-to-TVDB mapping issues. It also gives the next step: use add_series with the found ID. No explicit when-not or alternative search tools are mentioned, but the context is clear.

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