Search Images

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

With no annotations provided, the description must disclose behavioral traits, but it only states that the tool searches royalty-free images and supports filters. It does not mention read-only status, authentication needs, rate limits, or return format, which are relevant for an external API search tool.

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 a single, focused sentence that states the main purpose and key filters upfront. No unnecessary filler or repetition of schema details, making it highly concise and easy to parse.

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?

The tool has no output schema, so the description should explain what the search returns, but it does not explicitly mention the result type or structure. However, the schema fully documents parameters and the tool is a straightforward search, making the description minimally viable but not complete for returning data.

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 descriptions already cover all four parameters with clear explanations (e.g., query, page, limit, orientation). The description adds the context of royalty-free sources but does not add any new meaning beyond what the schema provides, so the baseline score of 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?

The description clearly states the tool's function: searching for royalty-free images from Pexels and Unsplash. This specific verb-resource pairing distinguishes it from sibling tools like search_images_batch, resolve_image_attribution, extract_image_query, and get_best_image.

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?

The description gives no explicit guidance on when to use this tool versus alternatives. It mentions supported filters but does not state when a user should choose this over search_images_batch or extract_image_query, leaving the agent to infer usage from the tool name alone.

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