google_auth

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

Discloses key behaviors: first call opens browser, token saved for reuse. No annotations provided, so description carries full burden. Could mention token expiration or re-authorization.

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 sentences, no fluff. Front-loaded with purpose, then prerequisites and behavior.

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?

Adequate for a simple auth tool. Covers purpose, prerequisite, and side effects. Could explain return value or token usage in other tools.

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?

Only one parameter with schema coverage 100% and description already covers path and default. Tool description adds little beyond schema, so baseline 3.

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?

Clear verb 'Authenticate' with specific resource 'Google OAuth2 for Gmail and Calendar access'. Distinguishes from siblings like google_auth_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?

States prerequisite (credentials.json) and first-call behavior (browser consent). Lacks explicit when-not-to-use or alternative tools like google_auth_status.

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