Run Playwright code (unsafe)

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

The description explicitly states 'Unsafe: executes arbitrary Python... RCE-equivalent', which goes well beyond the annotations (destructiveHint: true) to explain the severity and attack surface. No contradiction with annotations.

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?

The description is two sentences, front-loading the core action then the critical safety caveat. Efficient and clear, with no wasted words.

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?

Given the presence of annotations and schema that handle parameters, the description adequately covers purpose and safety. However, lacking output schema or return value info, and sibling differentiation is missing, but overall complete for the tool's risk profile.

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 67%, so the schema partially documents parameters. The description adds no parameter-specific details; it only repeats 'Python Playwright code' from the schema's code parameter description. Minimal added value.

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 tool runs Python Playwright code snippets and is uniquely identified as 'unsafe'. The verb 'run' plus 'Playwright code' makes the resource and action 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 explicitly state when to use this tool over siblings like browser_evaluate. The safety warning implies restricted use cases but lacks explicit context or exclusions.

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