account-switch

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

With no annotations, the description carries the full burden and largely succeeds: it discloses the OAuth trigger, the no-OAuth fast path, and the return payload (account email, newly-added flag, total count). It omits potential blocking/waiting behavior during the OAuth browser flow, but the main side effects are stated.

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 compact: three sentences cover behavior, conditions, and return values. It is mostly front-loaded, but 'smart mode' is an unexplained term that adds confusion without earning 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 output schema exists and the two optional parameters are fully documented, the description is reasonably complete. It explains OAuth behavior and return fields, but leaves 'smart mode' undefined and does not mention session-level side effects of switching accounts, which would be useful for an agent deciding whether to call this tool.

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%, giving a baseline of 3. The description adds meaning by explaining that email/alias can target an already-linked account and switches without OAuth, while absence of an email triggers account addition. This clarifies the relationship between the two optional parameters beyond their individual schema descriptions.

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 specifies the action (switching to or adding a Gmail account) and the resource (mcp-gmail account). It clearly differentiates from siblings like account-me, account-list, and account-remove by describing its switch/add behavior, though the phrase 'smart mode' is vague and slightly obscures the primary purpose.

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?

It provides explicit conditional guidance: if an email/alias is already linked, switch without OAuth; if unlinked or no email provided, trigger OAuth. This is clear context for when to use the tool, though it does not name alternative tools for account listing or removal.

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