TV show details

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds nothing beyond that — no note on caching, rate limits, or whether missing/unknown IDs error or return empty — so it is adequate but not enriching.

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?

One sentence, front-loaded with the scope ('one TV series') and then the field list; every clause earns its place with no 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?

For a simple one-param, idempotent read tool with an output schema present, the description is essentially sufficient — return values need not be explained and annotations carry safety. It would be marginally stronger with a one-clause pointer to how to obtain a tvId.

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?

With schema description coverage at 100%, the single tvId parameter is fully documented in the schema (TMDB id, sourced from search_tv_shows or discover). The description adds no additional parameter meaning, so the baseline 3 applies.

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 clear verb+resource (fetch full details for one TV series) and enumerates the returned fields, so the agent knows exactly what it gets back. The 'TV' qualifier implicitly separates it from get_movie_details and get_person_details, though it never names those siblings explicitly.

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?

Usage is only implied: 'for one TV series' plus the required tvId signals a single-item lookup after a search. There is no explicit when-to-use/when-not statement or pointer at search_tv_shows/discover (that pointer lives only in the schema param description).

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