Get TV cast & crew

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

Adds significant behavioral context beyond annotations: states cast limited to 20, lists crew roles, and importantly verifies that director/writer/creator credits are not reliably exposed (with examples). This complements the readOnlyHint and openWorldHint.

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?

Every sentence serves a purpose: purpose, limitation with evidence, alternative tools, source of ID. No fluff, well front-loaded, and structured logically.

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?

Given the output schema exists, the description compensates by explaining the structure (cast up to 20, specific crew roles) and limitations. It provides complete guidance for using this tool alongside its siblings.

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 covers the single parameter 'id' with description 'TMDB numeric id.' Description merely restates 'by TMDB id', adding no new semantic information. With 100% schema coverage, a 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?

The description clearly states the tool lists main cast (up to 20) and production crew by TMDB id. It distinguishes itself from siblings by detailing what it does not expose (director/writer/creator) and directs to alternatives.

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 provides when to use, when not, and alternatives: for creator credits use get_tv's created_by field, for episode specifics use get_tv_episode. Also mentions sourcing ID from search_tv.

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