configure_google_login

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

With no annotations, the description discloses that cookies are stored locally and may need re-extraction on expiry. However, it does not cover behavior on invalid cookies, rate limits, or other side effects.

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?

The description is concise, front-loaded with purpose, and covers key points in a few sentences. No unnecessary words.

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 no output schema, the description covers setup and usage adequately. However, it lacks information on verification of success, error handling, or expected outcomes.

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% with descriptions. The description adds context by explaining where to get cookies and that secure1psidts improves session stability, adding value beyond the schema.

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 switches to a free unofficial auth mode using consumer Gemini session. It specifies the mode supports image generation/editing but not video, distinguishing it from siblings like configure_api_key.

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?

It explicitly says when to use (switch to gemini-web auth mode) and provides step-by-step instructions for cookie extraction. However, it does not mention when not to use or direct comparisons to alternatives.

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