Smartest-TV

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

Discloses key behavioral trait (audio persists when screen off) beyond empty annotations, though omits other potential behaviors like transition effects or latency.

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?

Extremely efficient: front-loaded purpose statement followed by concise Args documentation with no extraneous text.

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 low complexity (2 simple params) and presence of output schema; minor gap in not explicitly contrasting with tv_power sibling.

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 clearly defining both parameters including boolean semantics and default TV selection behavior.

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?

Specific action (turn screen on/off) clearly stated and distinguished from tv_power via explicit note that audio continues when screen is off.

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?

Implies usage context (audio continues) allowing inference of when to use vs tv_power, but lacks explicit when/ when-not guidance or alternative mentions.

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