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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuine context beyond that: what the result contains (field name/label/type/required plus item count) and the workflow prerequisite. Pagination or ordering behavior is not mentioned, which keeps it off a 5.

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?

Two sentences, both earning their place: the first defines the output, the second defines the workflow position. The most important information (what it lists) is front-loaded.

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?

There is no output schema, so the description usefully enumerates the returned fields and item count, and it covers the prerequisite workflow. Only minor gaps remain (ordering, pagination, volume expectations) for what looks like a small per-site list.

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 site_id and user_goal are already documented; the description only implies site scoping. It adds no guidance on the optional user_goal parameter, so baseline 3 applies.

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?

Specific verb and resource ('List the catalog collections a site has') plus an enumeration of the concrete collection kinds (blog, menu, products, listings, help articles, events). This clearly separates it from siblings like list_collection_items (items, not collections) and list_dynamic_collections.

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 recommends calling it before adding or editing items, with the reason (use the real slug and field names). It gives a clear positive trigger but doesn't name the sibling alternatives it supersedes or any exclusions.

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