List Featured Pexels Collections

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so read-only behavior is covered. The description adds value beyond annotations by stating it 'Returns collection metadata only' and is 'paginated', which are behavioral specifics not captured in the annotations. This is informative without being redundant.

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 long, front-loaded with the core purpose, then includes an alternative, and ends with 'Read-only'. Every sentence adds essential information with zero fluff. It is concise and well-structured for quick scanning by an AI agent.

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 the tool has only two optional parameters fully documented in the schema, no output schema, and annotations covering read-only and open-world hints, the description is complete. It states the resource (featured collections), the scope (metadata only), the pagination behavior, and the path to get media—addressing all likely follow-up needs without requiring extra inference.

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 schema fully describes both parameters (page and per_page) with clear descriptions and defaults (100% coverage). The description mentions 'paginated' but does not add any additional meaning to the parameters beyond what the schema provides. Baseline of 3 is appropriate since the schema carries the explanatory weight.

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 the tool lists 'Pexels' featured collections' and specifies it is 'paginated'. It distinguishes from siblings by noting it returns 'collection metadata only', which separates it from pexels_get_collection_media and pexels_list_my_collections (featured vs. my). The verb 'list' makes the action unambiguous.

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 an explicit alternative: 'call pexels_get_collection_media for the photos/videos inside one', telling users exactly when to use a different tool. It also implies this tool is for collection metadata rather than media, giving clear usage context. The 'Read-only' note further guides safe usage.

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