pane_list

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the useful disclosure that the read returns live widget/pane state (explaining the non-idempotent hint) but says nothing about whether pane state can change mid-read or how the optional target_id/expected_layout_id guard behaves.

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?

A single dense sentence with the verb front-loaded and zero filler; each noun names a distinct piece of returned data.

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?

With no output schema, the description usefully enumerates what the agent gets back (widgets, geometry, active pane, per-pane markets/studies), which is the main missing piece. Minor gaps remain around result ordering and the guard parameter's effect on output.

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?

Both parameters have full schema descriptions (target_id from browser_list_tabs; expected_layout_id mismatch aborts before writing), so the schema does the heavy lifting. The description adds no additional meaning about either parameter, which matches the baseline of 3 at 100% coverage.

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 (Read) plus the exact resource set: retained chart widgets, pane geometry, active pane, per-pane markets/studies. It is more specific than the sibling pane_get_sync or pane_layout_options, but it never explicitly says how it differs from those sibling readers.

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?

There is no when-to-use guidance, no exclusions, and no mention of the alternatives in a crowded pane/browser sibling set (pane_layout_options, pane_get_sync, chart_get_state). The agent must infer that this is the pane-inspection entry point from the read verb alone.

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