Get Pexels Featured Collections

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

Beyond annotations (readOnlyHint, openWorldHint, idempotentHint, destructiveHint false), the description adds key behavioral traits: returns metadata only (no media URLs), the id field is the only needed follow-up, others are for human-facing selection, and 'no filters, just pagination'. No contradictions with 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?

Four sentences, each adding value. The first sentence states purpose, second gives usage guidance, third details return value, fourth clarifies limitations. No redundancy.

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 that an output schema exists (return values are predefined), the description covers all necessary context: purpose, when to use, what it returns, what to do with the result, and limitations. Complete for a paginated 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?

Schema description coverage is 0%, so description must compensate for the two parameters (page, per_page). It only mentions 'just pagination' but does not name or explain the parameters, their defaults, or their effect. This is insufficient for a low-coverage tool.

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 a specific verb ('Discover') and resource ('Pexels' editor-curated collections'). It clearly distinguishes from sibling tools by explaining that this is the only discovery path to get a collection ID, contrasting with pexels_get_collection_media for fetching media.

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?

Explicitly states when to use: 'USE WHEN you need a collection id and don't have one'. Also gives direct guidance to pipe the returned id into pexels_get_collection_media, and explains why it's the only discovery path.

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