revoke_oauth_token

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

The description discloses each step: API call, file deletion, cache clearing, and post-revoke behavior. Annotations are consistent (idempotentHint true, destructiveHint false align with token revocability). Provides full behavioral context beyond 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?

Three sentences: first states main purpose, second details the steps, third explains consequence and prerequisite. Every sentence adds value with no redundancy.

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?

With no output schema and no parameters, the description fully covers the tool's behavior, prerequisites (OAuth), and effects. Context among read-only sibling tools is complete.

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?

No parameters exist (schema coverage 100% via empty object). Baseline score of 4 applies as per rubric for zero-parameter tools; description adds no parameter info but none is needed.

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 it revokes the stored OAuth token and signs the user out. It specifies the exact actions (calls Google endpoint, deletes local file, clears cache) and distinguishes from sibling tools which are all read-only data retrieval tools.

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 indicates the tool requires OAuth and causes re-authentication for other tools. It does not explicitly state when to use versus alternatives, but no alternative revocation tools exist among siblings, making usage clear enough.

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