safari_list_tabs

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

With no annotations provided, the description carries the full burden. It discloses the output scope (includes user's own tabs), the cost (verbose), and the receipt feature ('Tabs this session owns carry a receipt'), which is genuinely useful behavioral context. It doesn't explicitly state read-only/non-mutating behavior, though 'list' strongly implies it.

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?

Two sentences with zero waste. Purpose is front-loaded, the verbosity warning earns its place as a cost signal, and the receipt note adds actionable guidance without padding. Appropriately sized for a 0-parameter tool.

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 zero-parameter, no-schema tool with no output schema, the description is complete: it states what is returned, the scope, the cost, and the preferred alternative. Nothing an agent needs to invoke or interpret this tool correctly is missing.

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 tool has zero parameters and schema coverage is trivially 100%, so the baseline is 4. The description adds no parameter meaning, and none is needed — there is nothing for an agent to misconfigure.

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 ('List every tab in this session's Safari window') and specifies the return content (titles + URLs). It also distinguishes itself from siblings by noting it includes the user's own tabs, which separates it from tab-management tools like safari_switch_tab and safari_close_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?

Provides clear context that the tool is 'verbose and rarely needed' and explicitly names an alternative ('Prefer keeping the receipt from safari_new_tab over listing'). However, it lacks an explicit positive condition for when to use it (e.g., 'use when you need to enumerate all tabs or recover a lost receipt'), so it stops short of full when/when-not guidance.

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