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

Annotations carry only a title, so the description bears the full disclosure burden. It does indicate the result shape (thumbnails plus original source pages), but says nothing about rate limits, pagination, cost, or whether it is a read-only network call, which matters for a web-facing search tool with no annotation coverage.

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 front-loaded sentence with no filler or repetition. It is efficient, though the brevity comes at the cost of the routing context an agent would need.

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 two-parameter read tool with a fully documented schema and no output schema, the description is minimally adequate and its mention of thumbnails and source pages partially compensates for the missing return schema. It still omits the one thing that matters here: how it differs from images_search and web_search.

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%, with both 'query' and 'limit' documented in the schema, so the baseline is 3. The description paraphrases 'images to find on the web' without adding format, syntax, or default behavior beyond what the schema already states.

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 gives a clear verb ('Search') and resource ('the web for images') and adds the return scope ('thumbnails and original source pages'). It does not, however, distinguish itself from the sibling images_search or web_search, so an agent cannot tell from the text alone which image-search entry point to pick.

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, no exclusions, and no mention of alternatives despite sibling tools images_search and web_search covering adjacent ground. The agent is left to guess whether this is the same as images_search or a distinct capability.

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