pristine_marketplace_collections

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

With no annotations, the description carries the behavioral burden. It usefully discloses that the storefront URL is fixed server-side and that valid empty result pages return 200 with an empty collections array, preventing an agent from treating empty results as failures. It does not describe error behavior or normalization details, but the important edge case is covered.

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 short sentences, each earning its place. The core action is front-loaded, and the additional details about normalization, fixed URL, and empty-page behavior are stated without redundancy.

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?

This is a simple read-only listing tool with two optional parameters and no output schema. The description is enough for an agent to invoke it correctly: it names the source, explains the fixed storefront, and clarifies empty-page behavior. It could describe the fields inside a normalized collection, but that is not necessary for making a correct call.

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?

The input schema already documents both parameters fully, including defaults and the limit cap. The description adds no parameter-specific meaning beyond what the schema provides, so the 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 states a specific action and resource: 'List Pristine Marketplace collections.' Adding that the collections are normalized and the storefront URL is fixed server-side makes the scope clear. It does not explicitly contrast with the closely named sibling pristine_marketplace_collection_products, but the resource is unambiguous.

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 when-to-use or when-not-to-use guidance is provided. The description never points an agent toward alternatives such as pristine_marketplace_products or pristine_marketplace_collection_products, nor does it explain under what conditions this tool should be preferred. Usage context has to be inferred entirely from the tool name.

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