browser_run_code_unsafe

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

Annotations already flag destructiveHint=true and readOnlyHint=false. The description adds critical context that the code runs in the Playwright server process (not just the page) and is RCE-equivalent, which is beyond what annotations express. This enhances safety awareness, though it does not detail side effects or error behavior.

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 efficient sentences front-load the purpose and critical safety warning. Every word adds value with zero redundancy or filler.

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 a dangerous code-execution tool with no output schema, the description adequately explains what it does and the risk. However, it could be more complete by mentioning expected return values or prerequisites (e.g., a page must be open). Still, the warning is strong and the schema covers parameters well.

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% with detailed descriptions for both 'code' (including an example) and 'filename'. The tool description itself adds no additional parameter information, so baseline 3 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?

The description clearly states the verb 'Run' and resource 'Playwright code snippet', and warns of unsafety and RCE equivalence. This distinguishes it from sibling tools that are specific browser actions (e.g., click, navigate), making its purpose unambiguous.

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 does not provide explicit guidance on when to use this tool versus alternatives. It only notes that it is unsafe and equivalent to RCE. There is no mention of preferred use cases or when to avoid it in favor of more specific browser actions like click or type.

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