playwright__browser_evaluate

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

The annotations already flag readOnlyHint=false and destructiveHint=true, so the safety profile is externally available. The description adds no further behavioral detail beyond the obvious fact that JavaScript is executed; it does not describe side effects, page mutation risks, or save behavior, but it also does not contradict the 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 a single well-structured, front-loaded sentence that uses every word for meaning. There is no padding or redundant restating of the schema.

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?

This is a powerful arbitrary-code-execution tool with no output schema and no examples or return format guidance. It lacks information about how results are returned, what side effects to expect, and how element targeting should be used, making the definition incomplete for the caller.

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?

The input schema has 100% description coverage and clearly documents target, element, filename, and function. The top-level description adds little parameter nuance, but the schema already carries the burden, so the 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 states a clear action and resource: it evaluates a JavaScript expression on the page or a target element. It is concise and unambiguous, but it does not differentiate itself from the similarly capable sibling playwright__browser_run_code_unsafe, so it falls short of a 5.

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 guidance on when this tool should be preferred over alternatives such as playwright__browser_run_code_unsafe, nor are prerequisites or exclusions stated. The only usage signal is the tool name and one-line purpose, which is not enough to route an agent reliably.

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