Commerce Promotion 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. "List" implies a read operation, but the description says nothing about authentication, rate limits, pagination behavior, or whether results are filtered by default.

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 one-sentence description is concise, but it is under-specified rather than appropriately sized. It front-loads the action but omits all operational detail, so the sentence does not fully earn its place as useful guidance.

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?

An output schema exists, so return values need not be explained. However, for a list tool with optional store filtering and pagination, the description omits parameter meaning and usage context, leaving the definition incomplete for correct invocation.

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 0% for three parameters (store_id, page_limit, page_offset), and the description provides no parameter meaning at all. It does not explain store scoping or pagination, failing to compensate for the undocumented schema.

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 clear verb and resource ("List commerce promotions"), so an agent can tell it returns promotions. However, it adds no scope details or sibling differentiation beyond the tool name, leaving it weaker than the high-quality examples that name exclusions or alternatives.

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 alternatives. It does not mention commerce_promotion_create, commerce_product_list, or any context such as filtering by store or pagination, so the agent receives no routing assistance.

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