Search Pixabay Videos

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

Beyond the readOnlyHint annotation, the description discloses that the tool returns a token-efficient summary with one representative video URL plus metadata, not the full size tiers. This adds valuable behavioral context about the output shape and resource efficiency.

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 exactly two sentences, front-loaded with the core purpose followed by essential behavioral guidance. Every word adds value, with no redundancy or filler.

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 an 11-parameter search tool with rich schema annotations and readOnlyHint, the description explains the return format and directs to get_video for full details. It provides sufficient context for an agent to invoke the tool correctly even without an output schema.

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% with detailed descriptions for all 11 parameters, so the description need not explain them individually. The generic mention of 'keyword and filters' adds no extra meaning beyond what the schema already provides.

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 specifies the tool searches Pixabay's royalty-free video library by keyword and filters, using a specific verb and resource. It distinguishes itself from sibling tools like pixabay_get_video, which retrieves full video size tiers for a specific ID.

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 directs users to call pixabay_get_video with an id for the full set of size tiers after receiving the summary, providing an alternative for complete data retrieval. This establishes when to use this search tool versus the get companion.

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