update_order

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

Annotations already mark readOnlyHint=false and destructiveHint=false. The description adds that it performs an update and returns '{success}'. It also clarifies the partial-update behavior. No contradictions, but could include error handling details.

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?

Two concise sentences with no redundant information. Every sentence adds value: the first states what the tool does, the second explains the partial-update and return format.

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?

Given the tool's complexity (15 parameters, partial update), the description covers core behavior and return. No output schema exists, but the return is simple. Slightly lacking on error cases and prerequisites, but adequate for an update tool.

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% with individual parameter descriptions. The description groups parameters into categories (status, customer, delivery, comments) and explains the partial-update semantics, adding moderate value beyond the schema.

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 'Update an order' with specific fields (status, customer, delivery, comments). It distinguishes from sibling tools like get_order, create_order, and orders_history by focusing on update functionality.

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 indicates 'Only the fields you pass are sent', implying partial update behavior. However, it does not explicitly state when to use this tool versus alternatives (e.g., create_order) or define prerequisites like order existence.

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