Apps Script MCP

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

No annotations are provided, so the description carries full burden. It mentions the OAuth flow completion but lacks critical behavioral details such as what happens upon completion (e.g., token storage, error handling, or authentication state changes). This is a significant gap for a security-sensitive 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?

The description is appropriately sized and front-loaded, with a clear purpose statement followed by a concise parameter explanation. Every sentence adds value without redundancy, making it efficient for an AI agent.

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 that an output schema exists, the description does not need to explain return values. However, as a complex authentication tool with no annotations, it lacks details on behavioral outcomes (e.g., what 'completion' entails). The parameter explanation is strong, but overall completeness is moderate due to missing operational context.

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 schema description coverage is 0%, but the description compensates fully by explaining the 'redirect_url' parameter in detail, including its purpose and an example format ('looks like: http://localhost/?code=4/0A...&scope=...'). This adds essential meaning beyond the bare schema.

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 specific action ('Complete the Google OAuth flow') and identifies the resource involved ('with the redirect URL'). It distinguishes itself from sibling tools like 'start_google_auth_tool' by focusing on the completion phase rather than initiation.

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 usage context by referencing 'the redirect URL from the browser after authorization,' suggesting it should be used after an OAuth flow has been initiated. However, it does not explicitly state when NOT to use it or name alternatives like 'start_google_auth_tool' for comparison.

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