Google Search Images

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 says 'Search Google Images' and references an endpoint; it does not disclose async/webhook behavior, execution_mode semantics, pagination, or result characteristics. The verb 'Search' weakly signals a read-only operation, but little else is 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 short and front-loaded, but it is under-specified for a 9-parameter tool. The clause 'with the documented /google-search-images endpoint' is redundant and does not earn its place, leaving the description closer to a name restatement than useful specification.

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?

Although the schema and output schema cover parameter mechanics, the description leaves key contextual gaps: no differentiation from google_search, no guidance on sync vs async, and no mention of webhook or regional/language behavior. An agent can invoke the tool, but not with confidence about when or how it behaves.

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 description coverage is 100%, so the baseline is 3. The description adds no parameter semantics beyond the schema, but the schema already documents query, limit, fields, region, language, webhook, execution_mode, uule, and async adequately.

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 states a clear verb and resource: 'Search Google Images.' This distinguishes it from the sibling google_search tool at a basic level. However, it mostly restates the tool's name/title and adds no scope or filtering detail, so it stops short of top-tier clarity.

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?

There is no guidance on when to use this tool instead of google_search or other sibling search tools. No context, exclusions, or prerequisites are provided, so an agent must infer usage from the tool name and schema.

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