Commerce Order Update

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it discloses nothing. It does not say whether the update is partial or full-replace, what happens to the null-defaulted fields, whether 'state' transitions are validated against workflow rules, what permissions are needed, or whether the change is reversible.

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?

It is a single short sentence with no padding, but this is under-specification rather than conciseness. The one sentence that exists conveys nothing beyond the tool's name, so brevity here is a defect, not an 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 values need not be explained, and that slightly lowers the burden. However, for a four-parameter mutation tool with zero annotation coverage and zero parameter documentation, the description leaves an agent with no basis for calling it correctly.

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% for four parameters, and the description supplies no compensating meaning for order_id, items, state, or billing_profile. Critically, it never explains the null-default semantics that determine whether omitting a field preserves it or clears it — a behaviorally decisive detail left entirely undocumented.

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 a verb (Update) and a resource (commerce order), so the basic operation is unambiguous, but it is essentially the tool name 'commerce_order_update' rendered as a sentence with no added scope. It gives no clue about how this differs from siblings like commerce_order_get, commerce_order_list, or commerce_order_create.

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 such as commerce_order_get for reads or commerce_order_create for new orders. The agent must infer everything about applicability from the tool name alone.

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