Open an app

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

Annotations already declare destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that the app must be installed and that identifiers can be names or Tizen IDs, but omits what happens on failure (app not installed) and whether launching changes TV foreground state or input source — relevant for a device-control 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?

One sentence, front-loaded with the action, with the examples and cross-reference packed in and no filler.

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 one-parameter tool with no output schema and annotations covering safety, this is nearly sufficient. The main residual gaps are failure behavior when the app is not installed and whether pairing/preconditions apply, which sibling tools like tv_pair hint at.

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 coverage is 0% and the single parameter is undocumented in the schema, so the description carries the load: it explains the accepted value forms with examples ('netflix', 'prime video') and the alternative Tizen ID sourced from tv_list_apps. Case-sensitivity and exact matching behavior remain unstated.

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?

A specific verb and resource — 'Opens an installed app' — plus concrete examples of accepted identifiers. It references tv_list_apps as the source of Tizen IDs, though it does not distinguish itself from tv_play_youtube, a sibling an agent could plausibly confuse with launching an app.

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?

Makes clear this is for launching already-installed apps and points the agent to tv_list_apps to obtain valid identifiers. It stops short of stating exclusions, e.g. that tv_play_youtube (not this tool) should be used to play specific video content.

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