safari_click

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It does not specify what happens after clicking, whether it waits for navigation, or any side effects (e.g., opening new tabs). This is insufficient for an agent to understand the tool's behavior.

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 sentence, which is too terse for a tool that likely requires additional context. It lacks any structure or detail, making it underspecified rather than concise.

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 no output schema, no annotations, and zero parameters defined, the description fails to provide enough context for an agent to use the tool correctly. It does not explain what constitutes a 'click' (e.g., left-click, right-click), what happens after, or any error conditions.

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 zero parameters, yet a click action likely requires specifying the target element. The description does not add meaning beyond the schema, failing to explain how the agent should indicate which element to click. With 100% schema coverage but no param info, baseline is 3, but the omission of necessary parameters reduces the score.

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 clicks an element in Safari, which is a specific verb-resource pair. It distinguishes itself from sibling tools like safari_read_tab and safari_search_tabs, which are read-only or search 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?

No guidance is provided on when to use this tool versus alternatives, such as safari_search_tabs or safari_wait_for, nor are any prerequisites or exclusions mentioned.

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