Open Chrome profile

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

With no annotations, the description carries the behavioral disclosure burden. It adds valuable non-obvious detail: when Chrome is already running, the tool verifies a genuinely new profile-bound window appeared and returns an error rather than a false success. This goes beyond the schema, though it stops short of describing exact return values.

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 three sentences long and every sentence earns its place: purpose, matching guidance, and the reliability edge-case. It is somewhat wordy but appropriately so given the non-obvious behavior when Chrome is already open.

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 single-parameter action with no output schema, the description covers the parameter, matching semantics, discovery prerequisite, and failure behavior. It does not spell out the exact success/error response shape, but that is not critical for a simple open action.

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?

Schema coverage is 100%, so baseline is 3. The description adds meaning beyond the schema by explaining matching by profile name or exact directory, giving concrete examples like 'Work' and 'Profile 1', and pointing to list_chrome_profiles.

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 states a specific verb and resource: it opens a new Chrome window under a specified profile. It clearly distinguishes itself from siblings like open_chrome_tab and list_chrome_profiles by focusing on launching a profile-bound window.

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 gives clear context: use profile name or exact directory, and consult list_chrome_profiles to discover available profiles. It does not explicitly contrast with open_chrome_tab or state when not to use it, but the usage context is unambiguous.

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