browser_run_code_unsafe

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

Description adds critical context beyond annotations: specifies execution in Playwright server process, RCE-equivalence, and unsafety. Annotations already set destructiveHint and openWorldHint, but description enriches understanding.

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 concise sentences: first states purpose, second warns of danger. No unnecessary words, each sentence earns its place.

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?

Provides essential warning and purpose, but lacks description of return value/output (no output schema) and does not summarize inter-parameter behavior (filename overrides code). Still, annotations and schema fill some gaps.

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 detailed descriptions (code includes example). The tool description does not add further parameter meaning beyond the schema, so baseline score is appropriate.

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?

Description clearly states 'Run a Playwright code snippet', which is a specific verb+resource. It distinguishes from sibling tools (e.g., browser_click, browser_evaluate) by emphasizing that this executes arbitrary JavaScript, not a specific action.

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?

Description warns 'Unsafe' and 'RCE-equivalent', implying use only when necessary, but does not explicitly state when to use this tool versus alternatives like browser_evaluate or other specialized tools.

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