store_update_shipping_zone

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

Annotations already indicate readOnlyHint=false, idempotentHint=true, and destructiveHint=false, providing basic safety profile. The description adds no additional behavioral context such as side effects, required permissions, or data scope. It merely repeats the action without elaborating on what gets updated or how.

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 sentence that essentially restates the tool name. While concise, it fails to add any informative content, making it wasteful rather than helpful. It is under-specified, not efficiently concise.

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?

There is no output schema, and the tool has 5 parameters including a nested countries array. The description provides no context on what fields are updatable, how to structure the countries array, or when to use this operation. It is insufficient for an agent to call correctly without relying solely on the 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?

All 5 parameters in the schema have descriptions (100% coverage), so the schema carries the burden of parameter explanation. The description provides no parameter-specific guidance, but per the rule, with high schema coverage a baseline of 3 is appropriate.

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 'Update Shipping Zone' states a clear verb and resource, but it adds nothing beyond what the tool name already conveys. It does not specify what aspects of the shipping zone can be updated (e.g., name, countries, rates) and does not differentiate it from sibling tools like store_create_shipping_zone or store_delete_shipping_zone beyond the verb itself.

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 guidance on when to use this tool versus creating, deleting, or listing shipping zones, nor any mention of prerequisites or context. The agent is left to infer usage from the name alone, which is insufficient.

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