accounts_add

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

No annotations are present, so the description carries the full burden. It usefully discloses that this is an OAuth-based connection and that it is stdio-only, implying a local interactive flow. However, it does not disclose side effects such as storing credentials, modifying the account list, or waiting for user interaction, nor does it mention reversibility.

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 one compact sentence with no filler. The key action, resource, and transport are front-loaded, and the high-value constraint 'stdio only' is included without extra prose.

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 zero-parameter tool with an output schema, the description is close to sufficient. However, it misses important operational context about the interactive OAuth behavior—such as opening a browser, blocking, waiting for user completion, and persisting the account—which an agent should understand before invoking it, especially with no annotations to fill the gap.

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 tool has zero parameters and an empty input schema, so schema description coverage is trivially 100%. Since there are no parameters to document, there is nothing the description needs to add; the zero-parameter baseline of 4 applies.

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 uses a specific verb ('Connect'), names the resource ('Gmail account'), and identifies the mechanism ('local loopback OAuth') and transport ('stdio only'). This clearly separates it from listing or removing accounts, but it does not explicitly distinguish it from the sibling accounts_auth_start, which could plausibly also involve OAuth.

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 phrase 'stdio only' provides a clear environment constraint, and 'Connect a Gmail account' implies the intended use case. However, there is no explicit guidance about when to use this tool instead of accounts_auth_start or any other alternative, and no prerequisites or exclusions are stated.

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