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

Annotations already declare readOnly/destructive/openWorld, so the bar is lower, yet the description adds real signal beyond them: it discloses the returned fields, the 100-per-page limit, the cursor handoff, and the auth requirement ('Cotlet API key with access to this app').

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 resource and returned fields are front-loaded in the opening sentence, followed by scope, ordering, workflow, pagination, and auth in tightly packed sentences with no 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?

With no output schema, the description carries return-value burden and does so by naming the returned fields, plus it covers pagination and auth prerequisites. It is complete for a list tool, missing only explicit edge-case behavior (e.g. empty results) to reach a 5.

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 coverage is 100%, so all three parameters (limit, query, cursor) are already documented in the schema; the description only reinforces query filtering and cursor paging. With the schema doing the heavy lifting, baseline 3 is appropriate.

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?

States a specific verb ('lists') and resource ('collections in your Client Gallery') and enumerates the returned fields (name, event date, photo count, gallery URL), so an agent can distinguish this list operation from pixieset_get_collection and pixieset_create_collection without opening any schema.

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?

Gives concrete usage guidance: 'Use query to find one by name, then pass its collection_id to the other tools,' and explains pagination handoff ('pass next_cursor back as cursor'). It establishes clear context but does not explicitly exclude alternatives such as get_collection, so it stops short of a 5.

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