BrowserEval

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

No annotations are provided, so the description carries the full burden. It discloses key access boundaries (DOM access, no Observable runtime) and typical safe use cases. It does not explicitly warn about mutating page state or side effects, but 'Execute JavaScript' strongly implies arbitrary code execution, so this is a meaningful but not complete disclosure.

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?

Three short sentences, front-loaded with the core action, followed by the key limitation, the alternative, and use cases. No filler or redundancy.

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 an arbitrary-JS tool with no output schema or annotations, the description covers purpose, environment boundaries, alternative tool routing, and typical use cases. The schema covers parameter details and the return behavior of the code parameter, so the main gap is a missing explicit note about potential page mutation/side effects, which is somewhat implied by 'Execute JavaScript'.

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 description coverage is 100%, so baseline 3 applies. The description adds environment context relevant to the code parameter but does not elaborate on label, notebook, or timeout_ms beyond what the schema already documents.

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 and resource: 'Execute JavaScript in the browser context.' It also explicitly differentiates from RuntimeEval by noting it does NOT access the Observable runtime, making sibling distinction immediate and clear.

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 routes the agent to RuntimeEval when notebook variables are needed, and identifies concrete use cases: DOM inspection, computed styles, and browser APIs. This gives both a when-to-use and a when-not-to-use/alternative.

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