Smartest-TV

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

Specifies 'toast' implying transient display, but lacks details on duration, visibility during playback, or error behaviors (no annotations to supplement).

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 with front-loaded purpose statement and clear Args section; no redundant content.

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?

Minimum viable for a 2-parameter tool; misses behavioral nuances (interruption level, persistence) that would help distinguish from tv_screen or tv_display given the large sibling set.

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 perfectly for 0% schema coverage by defining both parameters: 'Text to display' and 'Target TV name. 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?

Specific verb 'Show' + resource 'toast notification' clearly distinguishes this from sibling media/control tools like tv_play 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?

No guidance on when to use versus alternatives (e.g., tv_screen for persistent messages) or when notifications are appropriate.

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