create_shipping_zone

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

Annotations only include openWorldHint:false, providing minimal safety context. The description does not disclose behavior such as idempotency, required permissions, or reversibility. For a create operation, there is no mention of what the response contains or potential side effects beyond creation, leaving the agent to infer behavior.

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 extremely concise: two sentences with no redundant text. The first sentence clearly states the primary action, and the second adds a helpful sequencing note. It is front-loaded 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 provides a helpful next step (adding locations and methods) but is incomplete in other aspects. There is no output schema, and the description does not mention return values or error scenarios. Also, the mention of 'add locations' is ambiguous because no explicit 'add location' sibling tool exists, which might confuse an agent. Overall, it is adequate for a simple create but has gaps.

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 all parameters have descriptions. The tool description does not add meaning beyond the schema; it only hints that locations and methods are separate, which is not directly about the parameters. Therefore, 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 states 'Create a new shipping zone' with a specific verb and resource. It also distinguishes itself from sibling update/delete/list tools by indicating creation as the action. The follow-up instruction about adding locations and methods further clarifies its scope.

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 this tool: when creating a new shipping zone. It gives clear context that after creation, locations and methods must be added, which guides the workflow. However, it does not explicitly state alternatives (e.g., use update_shipping_zone for modifying existing zones) or exclusion criteria.

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