Smartest-TV

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

Discloses data sources (watch history + trending) but lacks details on caching, real-time vs. stale data, or whether recommendations update immediately after viewing.

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?

Front-loaded purpose statement followed by Args section; appropriately terse for a simple tool, though formatting is slightly informal.

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?

Adequate for the tool's simplicity given output schema exists; covers the 'how it works' and parameters, though could mention return type (shows vs. movies).

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?

Excellent compensation for 0% schema description coverage by documenting valid mood values ('chill', 'action', etc.) and limit semantics with defaults.

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?

Clearly states it gets personalized recommendations using watch history and trending data, distinguishing it from playback/control siblings, though it assumes 'TV content' is understood from the tool name.

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?

Provides no guidance on when to use this versus discovery alternatives like tv_whats_on or tv_history, nor when to omit parameters.

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