Close Google Account Browser

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

Discloses key behavior: preserves persistent profile on disk so reopening reuses login. No annotations provided, so description carries full burden; it effectively communicates the non-destructive nature and resource impact.

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?

Highly concise: three brief sentences plus a simple arg description. The first sentence immediately states the core purpose, and no redundant information.

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 and an output schema, the description covers the essential behavioral details (closing, session preservation, reuse). No gaps given the tool's simplicity.

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 only parameter, account_id, is described as 'The account id to close', which adds minimal value beyond the parameter name. Schema coverage is 0%, so the description should provide more detail (e.g., format, how to obtain it).

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?

Clearly states it closes the browser context for an account while preserving session. Differentiates from sibling tools like gv_delete_account (destructive) and gv_logout (session end) by specifying that the session is saved.

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?

Explicitly says 'Use this to free resources when done with an account', providing clear when-to-use guidance. Lacks explicit when-not-to-use or alternative suggestions, but the context is sufficient.

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