search_google_ai

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

With no annotations, the description carries full burden. It discloses that the tool uses the user's Firefox session, is free, grounded, and returns AI-synthesized answers with citations. It does not mention rate limits or side effects, but the key behaviors are transparent.

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 two sentences, front-loading the action and resource, then adding a valuable second sentence about the output and benefits. Every word earns its place; no 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?

Given no output schema, the description adequately explains the return value (AI answer with citations and source list). It also mentions the URL format and prerequisite (logged-in Firefox session). For a two-parameter tool, this is complete.

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% (both query and timeout_ms have schema descriptions). The description does not add additional meaning for the parameters themselves but provides context about the output format (AI-synthesized answer with citations). Baseline 3 is appropriate.

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?

Description clearly states it runs a Google AI Mode search and returns AI-synthesized answer with citations and source list. The verb 'Run a search' and resource 'Google AI Mode search' are specific. Though no sibling tools are listed, the description distinguishes it by mentioning 'free, grounded, no 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?

Description implies the tool requires a logged-in Firefox session and is free and grounded, but does not explicitly state when to use versus alternatives or provide when-not scenarios. The usage context is implied rather than direct.

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