safari_open

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

With no annotations, the description carries the behavioral disclosure burden. It openly discloses session reuse with cookies and extensions, tab navigation semantics, and default wait-for-load behavior so the returned title is accurate. It does not mention failure modes or permission caveats, but the major behavioral traits are covered.

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?

Three sentences with no filler. The core action is front-loaded, followed by the session context, then the parameter-dependent behaviors. Every sentence earns its place.

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 3-parameter navigation tool with no annotations and no output schema, the description covers purpose, session context, tab behavior, load behavior, and returned title accuracy. It lacks explicit error or edge-case handling, but an agent has enough information to call the tool 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?

Schema description coverage is 0%, so the description must compensate. It adds meaningful semantics for new_tab and wait_for_load, and even links wait_for_load to the returned title. The url parameter is minimally described as 'a URL,' but that is largely self-explanatory for a navigation tool.

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?

States a specific verb and resource: 'Navigate Safari to a URL.' It also distinguishes itself from a separate automation profile and, implicitly, from sibling interaction tools like safari_click or safari_read by focusing on navigation.

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?

Provides clear context by explaining that it reuses the real logged-in Safari session rather than a separate automation profile, which establishes a strong reason to use it. It also explains the new_tab and wait_for_load behaviors, though it does not explicitly name alternatives or say when not to use it.

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