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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuine behavioral detail beyond that: the default page size of 6, a hard cap of 200, and the exact response envelope (total, returned, offset, hasMore, nextOffset). It stops short of stating what happens on out-of-range offsets or whether the guide metadata is always present.

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?

Three tight sentences, front-loaded with the resource and its payload before the paging mechanics. The parenthetical "default 6 per page, max 200" duplicates the schema text for limit, a small redundancy that keeps the description self-contained but does not earn new information.

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?

For a two-parameter, zero-required read-only list tool with no output schema, the description supplies everything needed: scope, sibling routing, page-size bounds, the returned field names, and the iteration rule. Nothing an agent needs in order to call it correctly is missing.

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 both parameters are already documented and a baseline of 3 applies. The description goes slightly further by framing them as a paging contract — the next request should be issued with offset=nextOffset — which the per-parameter schema text only implies.

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 names a specific verb and resource ("List Shop by Aesthetic editorial collections") and states what comes back (counts and URLs), plus a secondary payload (relatedGuides for finish/texture/palette edits). It explicitly separates itself from get_collection, so an agent can distinguish the two without opening either 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?

It gives an explicit routing rule — use this tool for the editorial collection list, use get_collection for the detailed guides — and spells out the paging loop (call again with offset=nextOffset). It does not address how it differs from the plural sibling get_collections, leaving one plausible alternative unqualified.

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