Control Google Chrome

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

Annotations indicate not read-only and not destructive, but the description adds a behavioral requirement: it acts on a 'focused Chrome window,' which implies the need to focus Chrome first. It does not describe potential side effects (e.g., closing tabs) or failure modes. There is no contradiction with annotations.

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 very concise, two sentences, with the core purpose stated upfront. No fluff has to earn its place. The second sentence adds practical usage advice.

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 4 parameters and no output schema, the description gives a workflow but omits detailed explanations for what happens with each action (e.g., what happens when close_tab is used, whether confirmation occurs, how windowHandle affects behavior). It relies heavily on the schema for context but the schema has no descriptions. It is not fully complete for an agent to safely use all features.

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?

With a schema description coverage of 0%, the description must explain parameter meaning. It loosely covers 'url' (for open) and 'action' (for shortcuts/tabs), but completely ignores 'profile' and 'windowHandle'. The enum for 'action' is self-explanatory, but the additional parameters are left undefined. The description does not compensate for the low coverage.

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's purpose: 'Open a URL or send navigation/tab shortcuts to the focused Chrome window.' This uses specific verbs (open, send) and a specific resource (Chrome window), and distinguishes it from siblings like open_url (which may target any browser) and window_control (which handles window management).

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 provides a recommended usage sequence: 'For reliable GUI browsing, list windows, focus Chrome, act, then capture a screenshot.' This tells the agent when to use it and in what context. However, it does not explicitly mention when not to use it or provide alternative approaches, which is a minor gap.

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