Switch Active Google Account

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

With no annotations, the description discloses the state change, precondition, and scope of effect. It does not mention error handling or what happens with invalid account_id, but the core behavior is transparent.

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 plus a brief args line, no wasted words, and the key information is front-loaded. Every sentence 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?

For a simple switching tool with one parameter, the description covers purpose, precondition, and effect. It does not mention return values (output schema exists) or error cases, but is largely complete for the intended use.

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 description coverage is 0%. The description adds basic meaning for account_id ('The account id to make active'), but lacks format or source details. This partially compensates for the schema gap but could be more helpful.

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 explicitly states the verb 'switch' and resource 'active account', and clarifies that subsequent browser operations target this account, distinguishing it from siblings like gv_sign_in and gv_open_url.

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?

It clearly states the precondition (account must already be open via gv_sign_in) and the effect on subsequent calls, providing context for when to use this tool. It does not explicitly list alternatives but the precondition is informative.

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