Smartest-TV

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

With no annotations, description carries burden by mentioning built-in scenes exist, but omits side effects, idempotency, or what scene activation actually modifies.

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 Args/Examples sections; front-loaded purpose sentence makes efficient use of space.

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 basic invocation but lacks explanation of what scenes entail (which settings are affected) despite having output schema available.

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?

Compensates well for 0% schema coverage by documenting parameter meanings and conditional requirements (name required for 'run').

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 actions (run/list) and resource (scene presets) with built-in examples, distinguishing it from sibling TV control tools.

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 implied usage through examples showing list vs run patterns, but lacks explicit when/when-not guidance or comparison to alternatives like tv_power.

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