Commerce Shipping Method Create

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

No annotations are provided, so the description carries the full behavioral burden. It says nothing about required permissions, what the plugin parameter must reference, whether duplicate IDs are rejected, or what side effects creation triggers. For a write tool with zero structured behavioral hints, this is a major gap.

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?

A single, front-loaded sentence with no filler. It is concise and well-structured, though that brevity comes at the cost of substance rather than being elegant economy.

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?

An output schema exists, so return-value explanation is not required, but for a five-parameter write tool with 0% schema coverage and no annotations, the description leaves the agent without the information needed to call it correctly. It is inadequate for the tool's complexity.

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 0%, and the description mentions none of the five parameters. The required quartet (id, label, store_id, plugin) is entirely undocumented, and the role of the configuration object is unexplained. The description fails to compensate for the schema gap.

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?

States a clear verb+resource ('Create a new shipping method'), which is more than a tautology. However, it offers no differentiation from the two named siblings commerce_shipping_method_list and the many other commerce_*_create tools, and does not mention what a shipping method comprises (plugin, label, store).

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 when-to-use guidance, no prerequisites, and no mention of alternatives. An agent gets no help deciding between this and commerce_shipping_method_list when looking at available shipping-method tools.

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