Smartest-TV

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

Discloses 'screens off' mode but fails to explain behavioral interactions with overlapping sibling tools or side effects on TV state.

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?

Well-structured with clear sections (summary, args, examples); front-loaded purpose statement; every sentence earns its place.

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?

Covers all parameters and provides examples, but critically omits sibling tool relationships needed given the tv_play/tv_volume overlaps.

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 coverage: documents all 6 parameters including constraints (e.g., room vs rooms distinction, platform enum values).

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?

States specific purpose (multi-room audio with screens off) but doesn't clarify differentiation from sibling tools tv_play and tv_volume.

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 on when to use this vs tv_play (overlap on 'play') or tv_volume (overlap on 'volume' action), creating agent confusion.

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