browser_select

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

With no annotations, the description carries the full burden. It discloses the core behavior and side effect—loading the focused sample/preset—but does not mention what happens if no node is focused, whether the load can overwrite existing project state, or whether it is reversible.

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 a single efficient sentence with a parenthetical analogy. Every word adds meaning, and the core action is front-loaded.

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 zero-parameter trigger, the description is nearly complete: it names the action, the target, and the effect. It could be slightly more explicit about preconditions or failure behavior, but no essential calling information is missing.

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 tool has zero parameters and the schema covers 100% of them by being empty, so the description is not required to explain parameter details. The term 'focused browser node' refers to an implicit UI state rather than a parameter, which is acceptable.

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 uses a specific verb and resource: 'Activate the focused browser node.' It also adds the double-click analogy and the outcome 'loads the sample/preset into the project,' which clearly differentiates this from browser_navigate, browser_focused, and browser_preview.

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 'like double-click: loads the sample/preset into the project' phrasing gives clear contextual guidance on when this action is appropriate. It does not explicitly name sibling alternatives or state when not to use it, but the intended use is easy to infer.

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