update_shipping_zone_method

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

Annotations (idempotentHint=true, openWorldHint=false) already establish the safety profile. The description adds no behavioral context beyond what the schema already lists (e.g., parameters for enabled, title, order, settings). It is consistent with annotations and does not contradict them, but it does not disclose side effects, authorization needs, or response details.

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 that combines purpose and usage guidance with zero redundancy or filler. Every word contributes value.

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 mutation tool with 7 parameters and nested settings object, the description adequately covers the action and key use cases. It does not explain prerequisites like how to obtain zone_id/instance_id, but those are in the schema and can be inferred from sibling list tools. Given no output schema, the description is sufficiently complete.

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 all 7 parameters have descriptions. The tool description summarizes the main parameters (title, order, settings, enabled) but adds no new meaning beyond the schema. Baseline 3 applies since the schema carries the weight.

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 a specific verb ('update') and resource ('shipping method in a zone'), and enumerates concrete actions (enable/disable, change title, order, configure settings). It distinguishes itself from sibling tools like add_shipping_zone_method and delete_shipping_zone_method.

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 explicitly identifies when to use the tool ('Use to enable/disable, change title, order, or configure settings like cost'), giving clear context. It does not mention alternatives or exclusions, but the usage scope is unambiguous relative to siblings.

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