Smartest-TV

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

Discloses key behaviors not in schema: no args returns current status, None toggles mute, and implicitly that operations are atomic (get/set in one 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?

Front-loaded purpose statement followed by bulleted usage patterns and structured Args section; no redundancy, every line provides actionable guidance.

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?

Complete coverage of all 4 parameters including tv_name default behavior; defers return value details to existing output schema appropriately.

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?

Perfectly compensates for 0% schema description coverage by defining ranges (0-100), valid strings ('up'/'down'), and tristate logic (True/False/None) for mute.

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 verbs (get, set, step, toggle) with clear resource (volume), and 'All in one' phrasing distinguishes consolidated volume control from sibling tools like tv_audio or tv_power.

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?

Excellent explicit examples showing when to use each parameter combination (no args, level, direction, mute), though lacks explicit mention of alternatives/when-not-to-use.

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