list_collections

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

No annotations provided, so description bears full burden. Discloses readonly nature implicitly ('list') and pagination behavior, but does not explicitly state safety or error conditions. Adequate for a simple read operation.

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?

Very concise: three focused sentences covering purpose, return fields, pagination, and usage. No filler, each sentence earns its place. Front-loaded with primary action.

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?

No output schema, but description lists return fields. Covers pagination mechanics and query syntax. Lacks details on error handling or edge cases, but sufficient for a list tool with three simple parameters.

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%, and description adds value beyond schema by explaining cursor usage, query examples, and performance tip for 'first' parameter. Enhances usability without redundancy.

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?

Clearly states the action: 'List collections in the store, most recently updated first.' Specifies return fields (title, handle, ID, product count) and distinguishes from siblings like get_collection by stating it's used to find a collection's GID before other operations.

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?

Provides explicit guidance: 'Use this to find a collection's GID before calling get_collection, update_collection, or add_products_to_collection.' Also explains cursor pagination and query syntax. Lacks explicit 'when not to use' but offers clear context for its role.

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