Commerce Product List

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing. "List" weakly implies a read-only, non-destructive operation, but there is no mention of permissions, the pagination defaults (page_limit 50, page_offset 0), how the opaque filters object is interpreted, or whether results are store-scoped.

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?

It is a single, grammatical, front-loaded sentence with no waste, so it is concise by construction. The brevity is under-specification rather than discipline, and there is no structure beyond the one clause to help an agent.

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?

The presence of an output schema means return values need not be described, but that is the only gap covered. With no annotations, four undocumented parameters, an opaque filters object, and no statement of scope, the definition is not sufficient for an agent to invoke this tool confidently.

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?

All four parameters (filters, store_id, page_limit, page_offset) have 0% schema description coverage, and the description adds no meaning for any of them. The filters object in particular is a free-form additionalProperties object whose accepted keys are documented nowhere in either the schema or the 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?

The description names a specific verb and resource ("List commerce products"), which is enough for an agent to recognize a read/list operation on the commerce_product entity. It does not, however, distinguish this tool from sibling reads such as commerce_product_get or the sibling list tools (commerce_store_list, commerce_order_list, commerce_promotion_list), so the agent must infer scope from the name alone.

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?

There is no guidance on when to use this tool versus commerce_product_get, and no mention of prerequisites, store scoping, or pagination expectations. The agent receives only the bare verb "List" with nothing about the conditions that select this tool.

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