Tv Launch

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

No annotations are provided, so the description carries the full behavioral burden. It says what the tool does but does not disclose permissions, TV state requirements, whether launching replaces current playback, or other 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?

The description is three short, front-loaded lines with no filler. Each sentence contributes either the core action or the key routing alternative.

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?

For a three-parameter launch tool with full schema coverage and an output schema, the description covers purpose, key parameters, and sibling routing adequately. The main remaining gap is behavioral context, which is less critical here because return values are handled by the output schema.

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?

Schema description coverage is 100%, so the input schema already documents app, tv_name, and content_id. The description adds only the deep-link/content-ID usage distinction, which the schema also covers, so the baseline of 3 is appropriate.

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?

The description gives a specific verb and resource: launch an app, optionally with a deep link. It also explicitly distinguishes this tool from the sibling tv_play by contrasting exact content ID use against content-name use.

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?

It provides explicit routing guidance: use tv_play when you have a content name, and use tv_launch when you have the exact content ID. This covers when to use this tool and when to choose the primary alternative.

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