Smartest-TV

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

Explains the resolution and deep-linking flow but omits side effects (e.g., does it interrupt current playback?), error handling, or authentication requirements given no annotations exist.

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 mechanism explanation, structured Args list, and concrete Python-style examples that efficiently demonstrate parameter combinations.

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?

Adequately covers 6-parameter complexity with platform-specific logic and examples; output schema exists so return values need not be described, though error scenarios are missing.

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?

Fully compensates for 0% schema description coverage by documenting all parameters inline: platform values, query format, Netflix-specific constraints for season/episode, and title_id optimization.

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?

Explicitly states 'Find content by name and play it on TV' with specific mechanism (resolves ID, deep-links), and distinguishes itself as 'the primary tool' among siblings like tv_cast, tv_launch, and tv_resolve.

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?

Declares itself 'the primary tool' establishing default usage, and contrasts with tv_resolve by noting automatic ID resolution, though lacks explicit 'when not to use' exclusions.

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