Disconnect Google Workspace

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

Description states 'Remove' which implies destructive action, but annotations set destructiveHint=false. Additionally, description restricts to 'only the authenticated user's' credentials (scoped), while annotations set openWorldHint=true, suggesting broader effects. This direct contradiction warrants a score of 1.

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?

Single sentence with precise, front-loaded information. No unnecessary words or 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?

For a mutation tool that removes credentials, the description lacks context on side effects, reversibility, or output. Even with output schema present (not shown), the brevity leaves agents underinformed about the operation's impact.

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 description coverage is 100% for the single boolean parameter 'confirm'. The description adds no additional meaning beyond the schema, achieving baseline score for well-covered schemas.

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 verb 'remove' and the resource 'authenticated user's encrypted Google OAuth credentials', distinguishing it from sibling tools like connect_google_workspace or get_google_connection_status.

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 provides no explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or context. It only states what it does without directing agent decision-making.

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