image_search

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 usefully discloses a real behavioral trait beyond the schema – the 0.03 USDC on Base via x402 cost – and sketches the return shape, but says nothing about pagination, rate limits, or the payment flow beyond a price tag.

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?

A single tight sentence, front-loaded with the resource and keyword trigger, then cost and return fields. No filler, though the parenthetical cost clause slightly crowds the return-field list.

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?

For a 5-parameter, paid tool with no annotations and no output schema, the description is thin. It partially offsets the missing output schema by listing return fields, but leaves param semantics, pagination, and error/payment behavior unexplained.

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 only 40% (limit, language_code, location_code are undocumented). The description only references 'keyword', which the schema already covers, and adds no meaning for the remaining parameters. With a sub-50% coverage gap, it fails to compensate.

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?

States a specific resource ('Google Images results') and a trigger ('for a keyword'), and even names the return fields (image URL, page URL, alt text). It is clearly distinguishable from the other search siblings like news_search or maps_search, though it does not name an alternative explicitly.

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 when-to-use guidance and no alternative named. An agent must infer that this is chosen for image lookups over the sibling search tools; the description never states the condition that selects it or any exclusions.

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