Search Pixabay Images

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

With readOnlyHint and openWorldHint already in annotations, the description adds behavioral context by stating it returns a token-efficient summary (one representative URL plus metadata) and that get_image provides full size tiers. It does not disclose pagination counts or rate limits, but this is sufficient given the annotations.

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?

Two sentences, front-loaded with the primary action and resource, followed by output behavior and a redirect to a sibling tool. No filler or repetition.

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?

With 13 parameters and no output schema, the description clarifies the return format ('token-efficient summary', 'one representative image URL plus metadata') and points to pixabay_get_image for complete data. This is adequate for a search tool, though it could mention pagination behavior explicitly; the schema covers that via page/per_page.

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 100%, so the baseline is 3. The description only mentions 'keyword and filters' generically, adding no specific parameter meaning beyond what the schema already provides. Parameters like safesearch, orientation, and colors are fully documented in the schema.

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 uses a specific verb ('Search') and resource ('Pixabay's library of royalty-free images') with filters, clearly distinguishing from siblings. It also notes the token-efficient summary and follow-up call to pixabay_get_image, which differentiates it from the get and video search tools.

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 explicitly directs users to pixabay_get_image for full size tiers, providing a follow-up alternative. It implies use for image search rather than video search through the title and sibling context, but does not explicitly state when not to use it versus pixabay_search_videos.

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