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 burden. It mentions auto-detection of install location, but omits significant behavioral traits such as side effects (killing existing instances may discard unsaved state), what happens if TradingView is already running, or what the tool returns. The kill_existing warning is only in the schema, not the tool description.

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 exactly two sentences, front-loaded with the primary action and resource, and includes only necessary detail. No filler or repetition.

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 launcher tool, the core purpose is clear, but the description lacks context about behavior when an instance already exists, return values, and prerequisites like port availability. With no annotations or output schema, a bit more guidance would make it more complete.

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?

The input schema covers both parameters with descriptions (100% coverage), so the baseline is 3. The tool description adds nothing about parameters, but that's acceptable because the schema already documents them adequately.

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 clearly states the tool launches TradingView Desktop with Chrome DevTools Protocol enabled, using a specific verb and resource. It naturally distinguishes itself from siblings like tv_health_check or tv_update by describing the launch process, and adds cross-platform auto-detection detail.

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?

The description implies this is the entry point for launching TradingView with CDP, but it does not explicitly say when to use it relative to other tools, such as 'run before tv_health_check' or 'only if not already running.' No alternatives or exclusions are mentioned.

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