login_in_chrome

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

With no annotations, the description must carry the transparency burden. It discloses that the tool does not close Chrome and that user authorization is required, but it omits other behavioral traits such as whether a new tab is opened, whether the tool blocks while awaiting authorization, or how the callback URL is exposed to the user.

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 two short sentences with no filler. It front-loads the primary action and then gives a concrete follow-up instruction, making every word earn 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?

For a one-parameter tool with no output schema, the description covers the basic flow but leaves the practical outcome under-specified. It does not indicate what the tool returns or how the callback URL is obtained after authorization, which is a noticeable gap for an interactive OAuth flow.

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% with a single parameter 'storeUrl' described as 'The Shopify store URL'. The description does not add any additional meaning, but the schema already fully documents the parameter, so the baseline of 3 is appropriate.

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 uses a specific verb 'Start Shopify OAuth' and identifies the resource 'user's existing Chrome profile' plus a key constraint 'without closing Chrome'. It clearly distinguishes itself from the sibling 'complete_login_in_chrome' by positioning this as the initial step of a two-step flow.

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 clear workflow: start OAuth, then copy the final callback URL and pass it to complete_login_in_chrome. It implies this is for reusing an existing Chrome profile, but it does not explicitly state when to prefer this over sibling login tools 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.