list_discover_tv

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the endpoint path and parameter names but discloses no additional behavioral traits such as pagination behavior, default sorting, or response format. It does not contradict annotations, but it provides minimal extra context.

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 short but not effectively structured; it wastes space listing all parameters with the generic 'Query parameter' tag, which is repetitive and uninformative. The key information (purpose) is front-loaded, but the rest is filler rather than useful detail.

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 16 optional parameters, zero schema descriptions, and no guidance on filter combinations or defaults, the description is severely inadequate for an agent to call this tool correctly. It lacks any explanation of the discovery mechanism, expected output, or relationship to sibling discovery endpoints.

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 0%, so the description carries the full burden of explaining the 16 parameters. However, it merely repeats each parameter name followed by 'Query parameter', adding no meaning beyond what the property names already imply. It does not explain value formats, allowed values, or how parameters interact, leaving the agent to guess.

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 states 'Discover TV shows', which clearly indicates the verb (discover) and resource (TV shows), and it distinguishes from sibling tools like list_discover_movies and list_discover_tv_upcoming. However, it is essentially a paraphrase of the tool name and lacks any detail about what 'discover' entails (e.g., filtering, sorting).

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?

There is no guidance on when to use this tool versus alternatives such as list_discover_movies, list_discover_tv_upcoming, or list_search. No mention of prerequisites, typical use cases, or exclusions. The usage context is entirely implied by the name.

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