Smartest-TV

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

Discloses what data is returned (compensating for missing annotations), but omits other behavioral traits like idempotency, caching, or side effects.

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 concise, front-loaded with purpose, and uses standard Args format with no redundant 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 a simple read-only query tool; lists output fields even though output schema exists, providing sufficient context for invocation.

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?

Effectively compensates for 0% schema description coverage by explaining tv_name semantics ('Target TV name') and default behavior ('Omit for default TV').

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?

Clear verb 'Get' with specific resource 'TV status' and enumerates returned fields (app, volume, mute, model, firmware), implicitly distinguishing from sibling control tools like tv_volume 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?

Provides parameter usage guidance ('Omit for default TV') but lacks explicit guidance on when to select this tool versus siblings (e.g., when to query status vs. directly control).

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