Tv Next

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

With no annotations provided, the description carries the full behavioral burden. 'Continues from watch history' is useful context, but it does not disclose side effects such as changing TV playback state, required permissions, behavior when no history exists, or error conditions for an action tool.

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?

Two short sentences with zero waste. The primary action is front-loaded, followed immediately by the key continuation rule.

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?

The tool is simple, has no required parameters, and includes an output schema, so return values need not be explained. Still, as an action tool with no annotations, the description leaves behavioral gaps around side effects and prerequisite conditions that a more complete definition would cover.

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 100%, so both the 'query' and 'tv_name' parameters are already fully documented with defaults and omission behavior. The description adds no additional parameter meaning beyond what the schema provides, so the baseline of 3 is appropriate.

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 a specific verb and resource: 'Play the next episode.' It also explains the continuation logic via watch history, which helps distinguish it from a generic play command. However, it does not explicitly contrast itself with siblings like tv_play or tv_whats_on.

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?

The description implies usage when continuing a series, but offers no explicit when-to-use guidance, no prerequisites, and no mention of alternatives such as tv_play or tv_queue. The agent is left to infer that this is for resuming episodic content.

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