chrome_search_tabs

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

No annotations are provided, so the description carries full burden. It only states the action without disclosing behavior such as case sensitivity, how results are returned (e.g., list of tab IDs/titles), or whether it matches any substring occurrence. This is insufficient for an agent to predict outcomes.

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 short sentence that is front-loaded with the core action. It contains no fluff or redundant information. Every word is meaningful and earns its place.

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?

Despite having no parameters and no output schema, the description lacks critical context: how does the agent specify the substring if no parameters exist? Is it prompted from the user? Also, no indication of return type (e.g., matches, tab identifiers). This makes the tool's usage ambiguous for an AI agent.

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, so the baseline is 4. The description adds context that the tool searches 'for a substring', but since there are no parameters, it does not add meaning beyond what the schema implies. However, it is consistent and sufficient.

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 verb 'searches' and the resource 'rendered text of every open Google Chrome tab for a substring'. It distinguishes from sibling tools like chrome_list_tabs (lists tabs) and chrome_read_tab (reads a specific tab) by specifying the search action and scope.

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 usage guidelines are provided. The description does not mention when to use this tool versus alternatives like safari_search_tabs or other search tools. There is no guidance on prerequisites, limitations (e.g., only substring search, not regex), or when not to use it.

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