auth.setup

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

Discloses key behaviors beyond annotations: opens browser, returns immediately, 10-minute login window, skips if already authenticated. No contradiction with annotations (openWorldHint=true, readOnlyHint=false). The description adds significant context about side effects and limits.

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?

Front-loaded with core purpose and usage; troubleshooting section is separate. While not extremely concise, every sentence adds necessary context for a tool with user interaction. Structure is logical and scannable.

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 tool complexity (user interaction, auth flow), description covers setup, skip behavior, verification step, and failure recovery. Output schema exists, so return values don't need elaboration. No gaps identified.

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 coverage is 100%, so baseline is 3. The description adds value by distinguishing between show_browser (simple) and browser_options (advanced), and noting defaults. This clarifies parameter usage beyond schema definitions.

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 tool's purpose: Google authentication for NotebookLM access via manual login. It specifies it's for first-time authentication or when auto-login is unavailable, and distinguishes from 're_auth' for account switching. The verb 'setup' and resource 'authentication' are well-defined.

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?

Provides explicit when-to-use (first-time auth, no auto-login) and when-not-to-use (if already authenticated, use re_auth for switching). Also guides post-use verification with get_health and includes troubleshooting steps. This fully qualifies as explicit usage guidance.

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