Revoke Google Ads Access

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

The description discloses that the tool revokes OAuth grants and deletes local tokens, adding behavioral context beyond annotations (destructiveHint=true). No contradictions with annotations.

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 concise sentences, front-loaded with the action. No superfluous words, efficiently communicates purpose and usage guideline.

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 tool's simplicity (no required params, output schema exists), the description is largely complete. It could optionally mention confirmation or irreversibility, but not required.

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 description does not mention the single parameter 'response_format,' which has 0% schema description coverage. Schema defines it as an optional enum, but the description adds no value or guidance for its usage.

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 action: revoke Google OAuth grant and delete local tokens. It uses a specific verb and resource, distinguishing it from sibling tools like google_ads_exchange_code or google_ads_get_auth_url.

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?

Explicitly states 'Use only when the user explicitly wants to disconnect Google Ads,' providing clear when-to-use guidance. Does not mention alternatives or when-not-to, but context is sufficient for the agent.

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