Search Pexels Videos

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

Beyond the readOnlyHint annotation, the description reveals important behavioral details: it returns compact video objects, trims video_files to highest-resolution renditions, and references video_files_count for the full count. It also directs users to pexels_get_video for complete data, which adds transparency about data limits not evident from 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?

The description is two sentences, front-loaded with the core purpose, and each clause adds value: the filter list, return format, read-only note, and important trimming behavior. There is no wasted wording or duplication of schema details.

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 no output schema present, the description adequately explains what the tool returns (compact video objects with rendition links) and clarifies a critical data transformation (trimmed video_files). It also gives a cross-reference to pexels_get_video for complementary data, making the tool's behavior sufficiently complete for selection and invocation.

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?

The input schema already covers all six parameters with detailed descriptions (e.g., size enum, page defaults, locale examples), achieving 100% schema coverage. The description only summarizes these as 'optional orientation/size/locale filters' without adding new meanings; thus the baseline of 3 is appropriate since the schema does the heavy lifting.

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 'Search Pexels for videos matching a query' along with optional filters, making the tool's purpose specific and unambiguous. It distinguishes itself from sibling tools like pexels_search_photos by focusing on videos and from pexels_get_video by indicating it is a search operation.

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 provides clear context for when to use this tool—when searching videos by query—and explicitly names pexels_get_video as the alternative for retrieving the complete rendition list for a single video. It does not explicitly exclude other search variants like pexels_popular_videos, but the query-based filtering makes the usage context clear.

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