Search TV shows

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

Annotations already declare readOnlyHint=true and openWorldHint=true; the description adds that results are compact summaries and that the TMDB id is the required input for downstream TV tools. It does not contradict annotations and gives useful behavioral context beyond schema fields.

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 dense sentences, front-loaded with the core action and followed by usage guidance. No filler or redundancy.

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?

With a full input schema, output schema, read-only/open-world annotations, and a clear sibling distinction, the description covers the essential context for a search tool. It does not need to repeat return-value details because an output schema exists.

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% and each parameter (query, page, year, language, include_adult) already has detailed meaning. The description's phrase 'by name' adds slight emphasis on query behavior, but no additional parameter semantics are needed, so baseline 3 is appropriate.

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?

Description states 'Search TMDB TV shows by name' — a specific verb and resource. It also explains returns compact summaries with TMDB id and explicitly distinguishes from search_multi, earning full marks.

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 instructs 'Use this over search_multi when you already know the result is a TV show,' which both names an alternative and sets the condition for choosing this tool. It also notes get_tv and other TV tools require the returned id, clarifying downstream usage.

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