get_collection_products

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

The description uses 'Browse' implying a read operation, but does not explicitly state it is non-destructive or disclose behavioral traits like authentication needs, rate limits, or pagination behavior. Since no annotations are provided, the description should cover these, but it does not.

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?

The description is a single, front-loaded sentence with no unnecessary words. It efficiently conveys the core purpose.

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 simple list tool with two well-documented parameters and no output schema or annotations, the description is minimally adequate. However, it lacks details on ordering, field selection, and whether it returns all products or only a subset beyond the limit parameter. Completeness is average.

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?

With 100% schema description coverage, the schema already explains both parameters. The description adds no new semantic information beyond what is in the schema (the term 'handle/slug' is echoed). Baseline score of 3 is appropriate.

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 clearly identifies the tool's action ('Browse products') and the resource ('products within a specific collection'), specifying the key input ('handle/slug'). It is distinct from sibling tools like 'get_collections' (list collections) and 'get_product_details' (single product), though not explicitly differentiated.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention exclusions or contexts, such as preferring this over 'search_products' when the collection is known.

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