browser_open_tab

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

Annotations already declare openWorldHint=true, idempotentHint=false and destructiveHint=false. The description adds real value beyond that: it states the tool returns the new exact target ID (the handle needed for subsequent operations) and warns that opening a saved URL does not create an independent layout, which is a non-obvious side effect an agent would otherwise miscalculate.

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?

Two tight sentences, with the main action front-loaded and the return-value/caveat second. The saved-URL clause is slightly compressed and could be misread, but nothing is 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 mutating, non-idempotent browser tool with no output schema, the description supplies the return handle and a key side-effect caveat, and annotations cover the safety profile. Minor gaps remain on session prerequisites and what happens on failure, but the essentials for correct invocation are present.

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 all three parameters are already documented, including the expected_layout_id mismatch guard. The description only reinforces the target-ID concept; it adds no syntax, format, or interaction details beyond the schema, so the baseline 3 applies.

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 concrete verb and resource ('Open an HTTPS TradingView chart URL') plus the execution context ('dedicated Chrome session') and the return value. It partially differentiates from browser_navigate and layout_open via the target-ID return and the saved-URL caveat, but never names either sibling explicitly.

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 'HTTPS TradingView chart URL' qualifier and the saved-URL note imply when this applies, and the schema's 'target_id ... Required for changes' hints at the follow-up flow. However, there is no explicit 'use this instead of browser_navigate / layout_open when ...' guidance, so the agent must infer the routing.

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