add_shipping_zone_method

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

Without safety annotations (only openWorldHint: false), the description carries the burden. It states the action and that rates are configured later, clarifying scope, but does not disclose whether the operation is idempotent, fails on duplicates, or any authorization requirements. This is a minor gap for a simple add operation.

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?

Two sentences, front-loaded with the action, and every sentence contributes: the first states what the tool does, the second gives valid values and a follow-up step. No wasted words.

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 tool with 3 params, full schema coverage, and no output schema, this description covers the purpose, valid inputs, and post-add behavior. It lacks explicit return value info, but that is not critical given the 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 coverage is 100%, so the baseline is 3. The description adds value by explicitly listing valid method_id values and explaining that rates are configured after adding, which provides practical meaning beyond the schema's enum list.

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 'Add a shipping method to a zone,' which is a specific verb+resource. This distinguishes it from sibling tools like list_shipping_zone_methods, update_shipping_zone_method, and delete_shipping_zone_method by the operation type.

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?

Provides explicit guidance on valid method_id values and instructs the agent to configure rates via settings after adding, which clarifies the tool's scope. It does not explicitly mention alternatives, but the operation is self-evident and supported by sibling tool names.

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