Get Pexels Collection Media

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

Beyond the readOnlyHint annotation, the description discloses pagination, optional type filtering, compact shape with media_type tag, pre-sized URL options, and that video_files is trimmed while video_files_count gives the full count. This is valuable behavioral detail that cannot be inferred from annotations alone.

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?

Five sentences, each carrying substantive information. The first sentence front-loads the core purpose, and subsequent sentences add practical details about output shape and URL usage. It is somewhat dense but every sentence earns its place, with no repetition 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?

Given no output schema, the description thoroughly covers what the caller needs to know: return shape (compact, media_type-tagged), how to choose src URLs, video rendition trimming, and the alternative tool for full data. Pagination and filtering are mentioned, making it complete for a read-only list operation.

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 is fully described (100% coverage), so the baseline is 3. The description adds a little by mentioning filtering to 'just photos or just videos' and the pagination nature, but it doesn't go beyond what the schema already states for each parameter.

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 begins with a specific verb 'Get' and clearly identifies the resource: photos and/or videos inside a Pexels collection by its ID. This distinguishes it from sibling tools like search or list-collection tools, which focus on discovery or collection metadata.

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 sets clear context for when to use this tool (when you have a collection ID and want its media) and explicitly directs users to pexels_get_video for complete rendition lists, demonstrating awareness of alternative tools. It doesn't enumerate exclusions (e.g., when not to use), but provides sufficient practical guidance.

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