playwright_evaluate

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states what the tool does but doesn't describe execution context (e.g., page state, timing), error handling, security implications, or output format. This is inadequate for a tool that executes arbitrary JavaScript in a browser environment.

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, clear sentence with no wasted words. It's appropriately sized for a tool with one parameter and straightforward purpose, making it easy to parse and understand immediately.

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 complexity of executing JavaScript in a browser (with no annotations or output schema), the description is insufficient. It doesn't explain what the tool returns, how errors are handled, or the execution context, leaving significant gaps for an AI agent to use it 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?

The description doesn't add any parameter details beyond what's in the schema, which has 100% coverage for the single 'script' parameter. The baseline score of 3 reflects that the schema adequately documents the parameter, but the description doesn't provide additional context about script requirements or examples.

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 'Execute JavaScript in the browser console' clearly states the action (execute) and target (JavaScript in browser console), distinguishing it from other Playwright tools that perform UI interactions or navigation. However, it doesn't explicitly differentiate from potential JavaScript execution alternatives in the sibling list, though the 'browser console' context helps.

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 provides no guidance on when to use this tool versus alternatives like other Playwright tools for DOM manipulation or API calls. It lacks context about use cases, prerequisites, or exclusions, leaving the agent to infer usage based on the tool name and description alone.

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