products_get_product_collection

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the read-only nature is covered. However, the description adds no additional behavioral context. It does not explain pagination (limit/offset), the shape of the returned data (there is no output schema), or what happens when no filters are provided. Since the description carries little value beyond the annotations, and there is no output schema to clarify returns, a score of 2 is appropriate.

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 concise single sentence, 'Fetch Product Collections', which is clean and to the point. It is front-loaded with the core purpose and contains no fluff. However, it is perhaps too terse—it omits important functional details that could be added in a second sentence without becoming verbose. Still, as written, it demonstrates good structure and no wasted words.

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?

Given six parameters including pagination and search filters, and no output schema, the description is not complete enough for an agent to call the tool correctly. The agent lacks information about the return structure, how pagination works, or that filtering by name/collectionIds is possible. The annotations cover safety but not functional completeness. A more informative description explaining search and pagination behavior is needed.

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%, so all six parameters have descriptions in the schema itself. The description 'Fetch Product Collections' does not add any extra meaning to the parameters (e.g., clarifying that `name` is a partial match or that `collectionIds` is comma-separated). Since the schema already documents each parameter, the baseline of 3 applies; the description neither enhances nor detracts from parameter understanding.

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 'Fetch Product Collections' clearly states the action (fetch) and resource (product collections). It is a straightforward verb+resource statement that indicates a read operation. However, it does not differentiate from siblings like products_get_product_collection_id, but the plural form implies it returns multiple collections, which distinguishes it. Overall, it is clear and not misleading.

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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention that this is for listing or searching collections, nor does it contrast with products_get_product_collection_id (which fetches a single collection by ID) or the create/update/delete variants. The schema parameters (name, collectionIds) imply search capability, but the description does not surface this. An agent must infer usage from the schema alone, which is insufficient.

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