tmdb_tv_list

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

With no annotations, the description carries the transparency burden. It adds the credential-free auth context ('Credential-free public TMDB data') and states it returns a chart, indicating a read-only retrieval. It doesn't mention rate limits or response format, but for a data-fetch chart tool this is adequate.

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 sentences, 23 words, front-loaded with the core action. Every phrase adds value: the verb, resource, chart categories, and the credential-free note. No redundancy or filler.

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 14 optional parameters, all well-documented in the schema, the description need not repeat them. It provides the essential context (what data is returned, credential requirements). The lack of an output schema means the response format is not described, but for a chart-list tool the intent is clear.

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 coverage is 100%, providing baseline 3. The description adds meaningful context for the 'category' parameter by listing the four chart types (popular, top rated, airing today, on the air), which the schema does not. This enriches the 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 clearly states the tool's purpose: 'Get a TMDB TV chart' with specific chart categories enumerated (popular, top rated, airing today, on the air). This distinguishes it from sibling tools like tmdb_tv (likely show details) and tmdb_search (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 implies usage for chart-style TV data ('Returns a TMDB TV chart') but does not explicitly mention when to use it versus alternative TMDB tools or list exclusions. No alternatives or exclusions are named, so usage guidance is inferred rather than direct.

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