safari_search_tabs

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

With no annotations provided, the description must fully disclose behavior. It mentions 'rendered text' (not HTML source) and 'every open Safari tab', which gives some context. However, it does not explain whether the search returns matches for each tab, whether it is case-sensitive, or if it requires tab permissions, leaving behavioral gaps.

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 with no extraneous words, achieving good conciseness. However, it omits crucial information about the missing input parameter, which makes it less effective despite being brief.

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?

Without annotations or output schema, the description should explain return values and behavior comprehensively. It fails to state what the tool returns (list of tabs, snippets, or counts), whether searching is case-sensitive, or how multiple matches are handled. Significant gaps remain for effective use.

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 properties, but the description implies a required substring parameter ('searches ... for a substring'). This contradiction between description and schema creates confusion. Since schema coverage is vacuously 100%, the baseline is 3, but the contradiction reduces clarity significantly.

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 it searches rendered text of every open Safari tab for a substring, using specific verb 'searches' and resource 'every open Safari tab', which distinguishes it from sibling tools like chrome_search_tabs (Chrome) or safari_read_tab (read single 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?

The description implies it is for searching text across Safari tabs, but it does not explicitly differentiate from similar tools like chrome_search_tabs, nor does it provide guidance on when to use this tool versus reading individual tabs or listing tabs. Usage context is implied but not clarified.

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