Add a Google account

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

The description reveals that the tool initiates an OAuth flow and opens a browser for user sign-in, which is important behavioral context. However, it does not disclose post-conditions (e.g., the account being saved and available for other tools), potential blocking behavior, or any permission requirements. With no annotations, the description carries the burden but only partially fulfills it.

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 two sentences long and front-loaded with the primary action. Every word adds value, with no irrelevant details.

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 an interactive OAuth tool, the description conveys the essential workflow and the browser opening. However, given the absence of an output schema and annotations, a bit more detail about the result (e.g., what happens after sign-in) would make it fully complete. Still, it covers the core behavior sufficiently for a user to select and invoke the 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?

The input schema covers both parameters (name and openBrowser) with clear descriptions, so the global description need not repeat them. The description offers no additional semantic detail beyond what the schema already provides, resulting in a baseline score.

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 tool's function with a specific verb ('Start the OAuth consent flow') and a distinct resource ('connect a new Google account'). This distinguishes it from sibling account management tools like google_account_list/remove/status, which operate on existing 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 implies the tool is used for adding a new Google account, but it does not explicitly mention when to choose this over alternatives (e.g., listing or removing accounts). No exclusions or alternative tool references are provided, leaving use cases to be inferred from the name and sibling context.

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