update_order_details

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

With no annotations provided, the description carries the behavioral burden. It usefully discloses that omitted fields remain unchanged, which is important for a partial update. However, it does not mention side effects, required authorization, idempotency, or whether fields can be cleared by sending empty values.

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, tight sentence conveys the action, resource, affected fields, and update semantics. There is no filler or redundant restatement of the tool name.

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 seven parameters, a nested object, no output schema, and no annotations, the description is too sparse. It omits how the order is identified, what the caller should expect in return, and how this tool differs from overlapping siblings like edit_order.

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?

The description groups several parameters under broad labels ('shipment tracking', 'delivery address') but does not clarify individual semantics such as the distinction between trackingNumber and trackingCarrier, or that orderId identifies the target order. With only 43% schema description coverage, the description does not compensate enough for undocumented parameters.

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 the action ('Update order metadata') and lists the specific fields affected: customer email, internal notes, shipment tracking, PO number, and delivery address. However, it does not explicitly distinguish itself from the similarly scoped sibling 'edit_order'.

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 alternatives like edit_order or update_record. 'Only provided fields change' explains patch behavior but does not help an agent decide between this and sibling order-related tools.

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