ecommerce_setStoreShippingV1

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

The description discloses the side effect of creating a shipping zone, but does not mention idempotency, prerequisites, or whether the operation updates an existing price. With no annotations, this is partial transparency.

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?

Single sentence that is clear, direct, and contains no extraneous information. Well-structured and easy to parse.

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 description does not mention the output or return value, which is lacking for a tool without an output schema. It covers the basic behavior but misses what the agent can expect after calling.

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 coverage is 100%, so the schema already defines both parameters. The description adds no additional meaning beyond stating the price is for shipping and the zone creation implicitly involves the store_id.

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 clearly states the action ('Set') and the resource ('flat-rate shipping price for a store'), and also notes the creation of a shipping zone if needed. This sufficiently distinguishes the tool from sibling ecommerce 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?

No explicit guidance on when to use this tool vs alternatives or what prerequisites exist. The description only states what it does, not when it should be used.

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