Commerce Shipping Method List

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: no read-only guarantee, no pagination behavior (despite page_limit/page_offset), no store-scoping semantics, and no auth or rate-limit notes. For a bare list tool the risk is low, but the disclosure gap is real.

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?

A single short sentence is front-loaded and free of bloat, but here brevity reflects under-specification rather than efficient conciseness. Nothing is wasted, yet almost nothing is conveyed.

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, but with zero annotations and three undocumented parameters, the description is too thin for correct invocation. It lacks the store-scoping and pagination context an agent needs to call this safely and effectively.

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% and the description mentions none of the three parameters. An agent gets no explanation of what store_id scopes to, whether a null store_id means all stores, or how page_limit/page_offset interact. The description completely fails to compensate for the coverage gap.

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?

States a specific verb and resource ("List shipping methods"), so the basic operation is clear. However, it offers no differentiation from siblings such as commerce_shipping_method_create, and adds no scope detail (filtering, store scoping) that would let an agent distinguish it from other commerce list tools.

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 when-to-use guidance, no mention of prerequisites, and no routing to alternatives like the create sibling. The verb "List" only implicitly signals a read context, leaving the agent to infer usage entirely.

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