seerr_list_discover_tv

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

The readOnlyHint annotation already signals this is a safe read operation, but the description adds no behavioral context beyond that. It does not mention pagination behavior, filtering semantics, or whether any parameters are required for a useful response.

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 extremely short, but this is under-specification rather than effective conciseness. It lacks any structural elements such as context, parameter highlights, or usage notes that would help an agent invoke the tool correctly.

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 tool with 23 optional parameters and a complex discovery use case, this description is severely inadequate. It fails to mention the discover/filtering purpose, how to paginate, or how this differs from other TV discovery tools, making it nearly impossible to use correctly without external knowledge.

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%, and the description does not compensate by explaining any of the 23 parameters. The phrase 'Discover TV shows' provides absolutely no insight into how filters like genre, status, network, or certification should be used.

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 uses a clear verb and resource ('Discover TV shows'), correctly identifying the tool as a TV discovery listing operation. However, it does not distinguish this from siblings like seerr_list_discover_tv_upcoming or seerr_get_discover_tv_genre, which also relate to TV discovery.

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 guidance is provided on when to use this tool versus alternatives such as seerr_list_discover_movies or seerr_list_discover_tv_upcoming. There is no mention of usage context, exclusions, or preference over other discovery endpoints.

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