Popular Pexels Videos

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

The description discloses that video_files are trimmed to highest-resolution renditions and mentions video_files_count, and notes 'Returns compact video objects' – adding behavioral context beyond the readOnlyHint annotation.

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 sentences are packed with purpose, filters, response format, and an alternative tool reference; no filler words.

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?

Despite no output schema, the description explains response compactness, the trimming behavior, and where to get full renditions, covering the important behavioral aspects for a list tool.

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?

Input schema covers 100% of parameters with descriptions; the description only groups them as 'minimum width/height and duration range' without adding new semantics, so baseline score of 3 applies.

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 the specific verb 'List' with the resource 'currently popular Pexels videos' and further specifies optional filters, distinguishing it from sibling tools like search_videos and curated_photos.

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 pexels_get_video when complete rendition lists are needed, and states the tool is read-only, providing clear guidance on when to use this tool versus an alternative.

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