Open Google Account Browser (reuse session)

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

Beyond the openWorldHint annotation, the description reveals key behaviors: reuses existing saved session, no login window or waiting, and marks the account as active. No contradictions 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 concise at about 5 lines, front-loaded with the primary action, followed by differentiation, usage condition, side effect, and parameter. Every sentence adds value without redundancy.

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 simple tool with one parameter, no nested objects, and an existing output schema, the description covers purpose, usage, and behavior adequately. Minor omission: no mention of return value, but not critical given schema.

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 description adds minimal meaning for the single parameter account_id ('The account id to open'), which is only slightly more than the schema's title. Given 0% schema coverage, the description compensates to some extent but lacks detail on format or source.

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 'Open the browser context for an already-signed-in account', specifying the verb (open) and resource (browser context). It distinguishes itself from sibling tool gv_sign_in by noting that this tool reuses an existing session without a login 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 explicitly tells when to use: 'Use this after a sign-in has succeeded once and you've since closed the browser.' It contrasts with gv_sign_in and explains that it marks the account as active for subsequent tools, providing clear context for tool selection.

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