Set store shipping

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

The description goes beyond the annotations by disclosing a meaningful side effect: it will create the shipping zone if it does not yet exist. This helps the agent understand the operation is not purely a direct update, even though the annotations already correctly indicate it is mutating and not destructive.

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 single, front-loaded sentence with no filler. It states the primary action first and then adds the important side effect, making efficient use of the space.

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?

For a simple two-parameter mutation with complete schema descriptions and correct annotations, the description covers the core behavior and the key side effect. It does not explain expected response or return value, but that omission is minor given the tool's simplicity and absence of an output schema.

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 the schema already clearly documents both parameters, including price expressed in the smallest currency unit with 0 for free shipping. The description adds no extra parameter-level semantics beyond restating that the price is flat-rate and tied to a store.

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 ('Set'), resource ('flat-rate shipping price'), and scope ('for a store'), and even adds the side-effect that the shipping zone will be created if absent. This makes the tool's purpose clear and unique among the otherwise broad sibling list.

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 implies when to use the tool—when setting or changing flat-rate store shipping—but provides no explicit when-to-use or when-not-to-use guidance, nor any named alternatives. The context is adequate but the usage conditions are left to inference.

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