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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), and the description adds genuinely new behavior: results are HTTPS photo URLs usable in import_html_page/update_page, the photographer is returned, and English queries are preferred. One minor inconsistency is that the description implies an external Pexels search while openWorldHint=false, but it does not rise to a direct contradiction.

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?

Three front-loaded sentences with no filler, and the alternative-tool routing follows immediately after the primary scope. The second sentence is long and slightly run-on, and the parenthetical in sentence one costs a little clarity.

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 simple three-parameter read-only search with annotations covering safety and no output schema, the description covers purpose, alternatives, output format, and intended downstream use. The remaining gap is how count and orientation affect results, which the description never addresses.

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 0%, so the description must carry parameter meaning, and it only partially does: it gives the useful language preference for the required query parameter. The count (1-15) and orientation parameters are left entirely to self-explanatory schema constraints, with no guidance on defaults or when to set orientation.

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 specific verb and resource (search photos) and names the exact source (Pexels), plus clarifies that Pexels is not an exclusive restriction. It is slightly muddled by the parenthetical and is written in French while the rest of the tool ecosystem is English, but an agent can still tell what the tool does.

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?

It explicitly names the when-not case and the alternative path: for Google Images, proprietary images, or other sites, use the Web/browser tools and then import_image_url with the source file URL. That is a concrete routing rule rather than an implied one.

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