add_account

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

No annotations exist, so the description fully carries the burden. It discloses that OAuth opens a browser for authorization, stores token locally, and can time out, with a provided alternative. This is highly transparent for a connection setup tool.

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 sentences with no wasted words. First sentence states purpose and mechanism, second sentence provides a contingency plan. Every word 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?

Given the complexity of OAuth, the description explains the workflow, browser interaction, token storage, and timeout handling. No output schema exists, but the return behavior is sufficiently implied (account added or error). Siblings are all different, so no confusion.

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 coverage is 100%, so baseline is 3. The description mentions 'alias' in the fallback command but adds no new semantics beyond the schema descriptions for alias and email. It provides no additional parameter guidance.

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 it connects a new Gmail account via OAuth, using active verb 'Connect' and specific resource 'new Gmail account'. It distinguishes itself from siblings like list_accounts and message operations, as no other tool adds accounts.

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 explains when to use the tool (to connect an account) and provides an explicit fallback if OAuth times out (npm command). It doesn't explicitly state when not to use it, but the context and alternative are clear.

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