browser_list_tabs

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

Annotations already declare readOnly=true, destructive=false and openWorld=true, so the safety profile is covered; the description adds two genuine behavioral facts beyond them — results are filtered to eligible Superchart targets and browser cookies are never read. It still says nothing about pagination, ordering, or what happens when no eligible target exists.

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 sentences, zero filler, and the eligible-target scope is front-loaded before the privacy caveat. Nothing to trim.

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?

There is no output schema, and since downstream calls need an exact target ID sourced from this tool, an agent would benefit from knowing the return shape and whether non-Superchart tabs are silently omitted. The read-only annotations and full schema coverage make this adequate but not 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?

Schema description coverage is 100%, so both parameters (target_id, expected_layout_id) are already fully documented in the schema, and the description adds no meaning about them. Notably it never explains why a list tool accepts an expected_layout_id guard, which would be worth a sentence.

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?

States a specific verb and resource ('List ... browser targets') and narrows the scope to 'eligible TradingView Superchart' targets, which lets an agent distinguish it from browser_open_tab, browser_activate_tab, and browser_capabilities listings. It never names a sibling explicitly, so it stops short of full differentiation.

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 sentence says when to call this versus alternatives; usage is only implied by the schema note that target_id comes 'from browser_list_tabs' (i.e. discover tabs before acting on them). The negative scope statement ('never lists unrelated tabs') constrains results but is not usage guidance.

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