safari_open

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

The description adds meaningful behavior beyond the annotations: it discloses the side effect of opening a tab, the scheme normalization rule (adds `https://` when missing), the restriction to HTTP/HTTPS, and the need for Automation access to Safari.

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 three compact sentences, front-loading the primary action and then adding side-effect and permission notes. Every sentence contributes useful information.

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 simple one-parameter tool with an output schema, the description provides enough context to call it correctly: action, side effect, permission requirement, scheme behavior, and related sibling.

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 carry the parameter's meaning. It identifies the parameter as a URL and explains important semantics: missing schemes get `https://`, and only HTTP/HTTPS are accepted.

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 precise verb and resource: opening a URL in a new Safari tab. It also distinguishes the tool from the related `safari_tabs` sibling by pointing to it for tab-related operations.

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 tool's intended use is clear from "Open a URL in a new Safari tab," and it references `safari_tabs` as the related alternative. However, it does not explicitly state when to use this tool versus inspecting tabs with `safari_tabs`, nor does it describe exclusions.

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