safari_evaluate_js

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

No annotations provided, and the description omits important behavioral details such as security implications, page state changes, error handling, or how the script is supplied.

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 one-sentence description is too sparse; it lacks essential details about script input and behavior, sacrificing completeness for brevity.

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 tool's complexity (executing arbitrary code), the description fails to explain how to provide the script, return format, or error handling, leaving a critical gap.

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 is empty, implying no parameters, but the description claims it runs arbitrary JavaScript—there is no explanation of how the script is provided, making the tool unusable as described.

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 executes arbitrary JavaScript in the current Safari tab and returns the result, distinguishing it from sibling tools like safari_click or safari_read_tab.

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?

No explicit guidance on when to use this tool vs. alternatives like chrome_evaluate_js or other Safari-specific actions, though the purpose is clear from the name and description.

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