remove_account

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

With no annotations supplied, the description carries the full burden and does disclose the key traits: this is destructive (token revoked and deleted) and requires a two-step confirmation, which is the safety-relevant behavior. It omits what happens to any synced email/draft data and whether re-authorization is required afterward, leaving some destructive-side-effect detail unstated.

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?

Two short sentences with no filler; purpose and the destructive effect come first, then the two-step contract. Every clause 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 destructive two-parameter tool with no annotations and no output schema, the description covers purpose, the destructive effect, and the confirmation handshake — enough to call it correctly. It is slightly short on post-removal state and error conditions, but nothing critical to invocation is missing.

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%, so the description must compensate, and it does: 'account' is defined as an email or alias, and 'confirm_token' is explained as a value returned by the first call and passed back on the second. It adds meaning for both parameters, though it doesn't describe accepted formats for the account identifier or validation failures.

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?

States a specific verb and resource ('Disconnect a Gmail account') plus the exact mechanism ('revokes and deletes its stored token'). It is clearly separable from siblings like add_account, assign_account, and list_accounts without opening either schema.

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 gives the operative usage procedure — first call returns a confirm_token, second call with that token performs the removal — which tells the agent how to sequence invocations. It does not explicitly state when to prefer this over assign_account or what to do if the account is unknown, so it stops short of full when/when-not guidance.

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