set_browser

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

No annotations are provided, so the description must fully disclose behavior. It only states 'Switch browser' without mentioning side effects like session resets, permission requirements, or impact on existing state. This is a significant gap for a configuration-changing tool.

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, front-loaded sentence with no waste. It efficiently conveys the core purpose. Slightly more context could be added without sacrificing conciseness.

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 one parameter, no annotations, and an existing output schema, the description should clarify what the tool returns or confirms. It fails to mention if the switch takes effect immediately or requires a page reload. The output schema is present but not explained.

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 schema has 0% description coverage and no enum values. The description compensates by listing the three allowed browser types, which adds meaning beyond the schema. However, it does not specify exact string format (e.g., case sensitivity) or that these are the only valid values.

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 clear verb ('Switch') and specifies the resource ('browser'), listing three specific browser types (chromium, firefox, webkit). This distinguishes it from sibling tools like set_headless or navigate, which have different purposes.

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 description states what the tool does but provides no guidance on when to use it versus alternatives or any prerequisites. While sibling tools are distinct, it would benefit from mentioning that it should be used before navigation to change the browser engine.

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