discover_tmdb_media

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

No annotations are provided, so the description must carry the full burden. It only states '探索' and mentions returning a media list, but does not clarify read-only nature, pagination behavior, authentication requirements, or any side effects. This is minimal disclosure.

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 brief, front-loaded with a clear purpose sentence, and uses a clean Args/Returns structure. It contains no fluff, though it could still be informative within the same length.

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 tool's complexity (many filter options inside TMDBDiscover) and lack of output schema, the description is under-specified. It does not explain the structure of filters or the shape of the returned list, which is insufficient for correct invocation.

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 lists only 'filters' and 'page' with generic Chinese labels, adding no meaning beyond the schema. With 0% schema description coverage and a complex TMDBDiscover object, the description fails to compensate, leaving the agent without explanation of filter semantics or page usage.

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 '探索TMDB电影/电视剧' with filter conditions, identifying a specific verb (explore), resource (TMDB movies/TV), and scope (based on filters). This distinguishes it from sibling tools like discover_douban_media and search_media_or_person.

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?

No explicit guidance is provided on when to use this tool versus alternatives. The description only implies use for filtered TMDB discovery but does not mention sibling tools or exclusions, leaving the agent without clear decision criteria.

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