pane_select

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

Discloses that the tool makes a pane active and that subsequent calls target that pane. This adds context beyond annotations (openWorldHint=false, idempotentHint=true) by explaining the state change and flow. No contradictions.

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 concise sentences, front-loaded with the action and effect. Every sentence is necessary and informative.

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 simple tool with one parameter and no output schema, the description fully explains purpose, effect, and source of IDs. No gaps.

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 covers the single parameter 'id' with description. The description adds 'Find ids with pane_list,' which reinforces but doesn't add new meaning. Baseline 3 for high schema 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?

Clearly states the verb 'Make a pane active', the resource 'pane', and the effect on subsequent browser_*/repro calls. Distinguishes from sibling tools like pane_list and pane_close.

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?

Explicitly says to use when targeting a pane for subsequent actions, mentions source of IDs (pane_list), and notes the constraint '(Cockpit only.)' Does not explicitly state when not to use, but context is clear.

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