tabs_list

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

With no annotations, the description carries the full burden, and 'List every open ... tab' makes the read-only, non-mutating nature unambiguous. It also discloses the shape of what comes back (id, title, URL), which is the key behavioral fact for a caller. The remaining gap is that it does not say whether all windows/private tabs are covered or how results are ordered.

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?

A single front-loaded sentence with no filler; the scope, resource and returned fields all land immediately.

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?

There is no output schema, so the description must convey the return shape and it does (id, title, URL). It stops short of saying whether results span multiple windows, include non-active tabs, or are ordered, which an agent may want before enumerating.

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?

Zero parameters, so there is nothing parameter-level to explain and the baseline applies. The description usefully clarifies that the output includes an id alongside title and URL rather than only naming the parameters.

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?

Specific verb ('List') plus specific resource ('every open Safari tab') and it names the returned fields. It is clearly distinguishable from siblings like tabs_select, tabs_close, read_page and get_page_text, which act on a single tab or page content.

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 scope 'every open tab' implies it is the enumeration step before tabs_select/tabs_close, and the result fields suggest a discovery role. But it never says when to prefer this over read_page or get_page_text, or that selection/close requires an id first.

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