Get Shopify Collections

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so safety is covered. The description adds the return-field profile (SEO fields, sort order, template suffix), which is genuinely useful, but it says nothing about pagination behavior or how the default limit of 10 interacts with the maximum of 250.

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 short, front-loaded sentences with no filler. The listing behavior comes first and the return payload second.

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?

Absent an output schema, the description reasonably covers the return fields, which is the right use of that space. However, for a list tool with a pagination-style limit parameter and no schema descriptions, the missing information about truncation and result count leaves an agent unable to predict the response size.

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%, so the description carries the full burden. It explains searchTitle semantically ('search by title') but says nothing about 'limit' – its default of 10, its ceiling of 250, or whether it caps the returned list. Half the parameters remain undocumented in both schema and description.

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+resource ('List all collections') plus the search variant, which is enough to distinguish it from mutation siblings like shopify_create_collection and shopify_update_collection. It also names the returned fields. It stops short of explicitly naming an alternative tool.

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?

'List all collections or search by title' implies the branch condition for using searchTitle, so usage is inferable. But there is no explicit when-to-use/when-not guidance and no pointer to sibling collection tools such as shopify_update_collection or shopify_collection_add_products.

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