browser_run_code

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

No annotations are supplied, so the description carries the full burden. It implies persistence ('resident browser daemon') but says nothing about whether the code runs sandboxed, what page/DOM access it has, mutation risk, timeouts, or error behavior for arbitrary Python — significant gaps for a code-execution 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?

A single front-loaded sentence with no filler, which is structurally clean. It is arguably terse to the point of under-specification for a high-risk execution tool, but there is no wasted text.

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?

An output schema exists so return values need not be explained, but for a tool that executes arbitrary Python in a live browser with zero annotations and zero parameter documentation, the description omits what an agent must know to call it safely and correctly.

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 0% with two parameters. The phrase 'Python automation code' incidentally conveys the language for 'code', but nothing is said about available APIs, globals, or context. 'tab_index' is completely undocumented in both schema and description, including whether it defaults to the active tab.

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 (Execute) and resource (Python automation code in the resident browser daemon), which is clearer than a generic 'run code'. It does not, however, distinguish itself from close siblings like browser_evaluate or browser_batch, so an agent cannot tell from the text alone which execution surface to pick.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives. With siblings such as browser_evaluate, browser_batch, and browser_get_content present, the description leaves the routing decision entirely to inference.

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