google_ai_mode

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

No annotations are provided, so the description carries the full burden. It only states the fetch action and operation names, without disclosing behavioral traits like authentication needs, rate limits, output format, or side effects. The POST variant is mentioned but its unique behavior is not explained.

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 the primary purpose, and uses a clear structured list for operations. Every sentence earns its place with no filler.

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?

The description provides enough to invoke the operations but lacks an output description, error handling, and rationale for having two near-identical operations. Since there is no output schema, some return-value or behavior information would improve completeness.

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?

The schema descriptions are generic, but the tool description adds the required 'prompt' parameter for each operation. However, it does not elaborate on prompt content or format beyond being a query, and the args object is open-ended.

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 fetches Google's AI Mode conversational answer for a query, using a specific verb and resource. It distinguishes from sibling tools like gemini or ai_overviews by explicitly naming Google's AI Mode.

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?

Usage is implied: use this tool when you need Google AI Mode answers. It lists the two operations and their required prompt parameter, but does not explicitly compare to alternatives or state when one operation should be preferred over the other.

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