seerr_get_tv_recommendations

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

The readOnlyHint annotation is the only behavioral signal, which the description does not expand upon. It adds no details about pagination, language handling, or what the response contains. Beyond the annotation, the description discloses nothing operational.

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 a single, short sentence with no wasted words, which is economical. However, it is so under-specified that it crosses from concise into insufficient, lacking essential operational context that should accompany the purpose.

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?

This is a minimal description for a tool with a required tv_id parameter. It does not mention that the tool requires a TV ID, nor does it clarify the relationship between the input and output. Even with an output schema present, the description is too incomplete to be effectively used.

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 0% schema description coverage, the description should compensate, but it does not mention tv_id, page, or language. The schema's parameter names are somewhat self-explanatory, but the description adds zero meaning, leaving the agent without any elaboration on parameter 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 'Get recommended TV series' uses a specific verb and resource, clearly indicating that the tool retrieves TV recommendations. However, it does not specify that recommendations are based on a particular TV ID (tv_id), which could differentiate it from other recommend/similar tools.

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 vs. alternatives such as seerr_get_tv_similar or seerr_get_movie_recommendations. The description provides no context for selection, no exclusions, and no mention of prerequisites like requiring an existing TV ID.

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