open_browser

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

Discloses blocking nature (pauses server) and purpose, but lacks details on prerequisites (e.g., GUI environment), failure modes, or security implications. No annotations to supplement.

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 short sentences, front-loaded with primary action and purpose. Every word earns its place; no repetition or fluff.

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?

Adequate for a simple tool with one optional param and no output schema. Could mention that it requires a graphical display environment, but overall complete enough for a competent agent.

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 coverage is 100% with exact same description as in schema. Tool description adds no extra meaning beyond what the schema provides for the single parameter, so baseline 3.

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 it opens a headed browser for manual CAPTCHAs or login, distinguishing it from sibling tools like scrape (automated). Verb+resource+use case explicit.

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?

Implies use when human intervention for CAPTCHAs or login is needed. Context is clear, but no explicit exclusions or alternative comparisons to siblings.

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