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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered structurally. The description adds genuinely new context not in annotations: the credit cost ('Flat 5 points per successful run') and the concrete set of returned fields (title, description, image, product count, timestamps), which substitutes for the missing output schema.

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 sentences: identity and scope first, then the return payload and cost. No filler, every clause carries 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?

No output schema exists, and the description compensates by enumerating the returned fields; cost and network scope (openWorld annotation) are covered. It stops short of describing failure behavior for an unknown handle or domain, which would matter for a single-record lookup.

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 100% and both parameters (store_domain, collection) are already documented with examples in the schema. The description only restates 'by store domain and handle', adding no syntax or format detail beyond the schema, so the 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?

States a specific verb and resource ('Get one Shopify collection') plus the return fields, which distinguishes it from the sibling product/collection-product tools. It never explicitly names an alternative, but 'one ... collection' plus the required store_domain/handle makes the singular-lookup scope clear.

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?

'By store domain and handle' implies you must already know the collection handle, which nudges an agent away from using this for discovery, but the description never says so outright. No when-not-to-use or named alternative (e.g. run_shopify_collections_products, run_shopify_products_search) is given, so usage is only implied.

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