pexels_my_collections

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clarifies that only the authenticated user's own collections are returned, implying an auth requirement and read-only nature. However, it does not disclose error cases, rate limits, or pagination behavior beyond what the schema hints at.

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 a single concise sentence, front-loaded with the action ('List') and scope ('authenticated user's own'), with no filler words. It is appropriately minimal for a straightforward list operation.

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 absence of annotations, an output schema, and any parameter descriptions, the description is minimal. It explains the core function but not the structure of returned collections, pagination behavior, or special cases, leaving significant gaps for an agent preparing to invoke the 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%; the description does not mention the 'page' or 'per_page' parameters at all. While the parameter names are conventional, the description adds no semantic meaning to the schema, leaving the agent to guess about pagination defaults and behavior.

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 ('List') and resource ('authenticated user's own Pexels collections'), clearly distinguishing it from sibling tools like pexels_featured_collections and pexels_collection_media. The scope is unambiguous and directly tied to the tool name.

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 implies usage for retrieving the user's personal collections, but it does not explicitly contrast it with alternatives such as featured collections or mention when not to use this tool. The context is clear but guidance on alternatives is only implicit via the sibling names.

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