Remove a Google account

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

The description discloses one important side effect—deleting stored tokens—but does not clarify whether the removal is permanent or reversible, what happens to connected services, or any authorization requirements. With no annotations to buffer, the description carries the full burden of behavioral disclosure, and this is insufficient for a destructive operation.

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 a single sentence that gets straight to the point. It is concise, front-loaded, and contains no unnecessary words.

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 no output schema, the description covers the basic action but lacks important contextual details such as reversibility, impact on the default account, and whether the account is removed from all Google services. It is minimally adequate but leaves notable gaps for a destructive operation.

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 schema fully describes the only parameter 'name' as 'Account nickname to remove,' and the tool description adds no further meaning. Schema coverage is 100%, 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 clearly states the action: 'Disconnect an account and delete its stored tokens.' This specifies the verb and resource, and distinguishes the tool from siblings like google_account_add, google_account_status, and google_account_set_default. It unambiguously communicates the tool's function.

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 no guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. It does not mention that this is a destructive action requiring caution, or what happens if the account is the default one. Without this context, the agent may misuse the tool.

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