tiendanube_update_order

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

Discloses that updates are limited to certain fields after order creation to maintain data integrity. Lists the allowed statuses, which aligns with the enum. No annotations exist, so description carries the transparency burden well.

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?

Three sentences, each serving a distinct purpose: action summary, specific use cases, and limitation note. No unnecessary words, direct and front-loaded.

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 low complexity (3 parameters, no nested objects, no output schema), the description covers the main use cases and limitations. Missing mention of prerequisites like order existence, but that is implied by 'existing 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?

Schema coverage is 100%, so the schema already describes each parameter. The description adds value by grouping fields (status, owner notes) but does not provide details beyond what the schema offers (e.g., format of owner notes). Baseline 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?

Clearly states the action (modify specific fields) and resource (existing order). Enumerates the modifiable fields (status, owner notes) and differentiates from order-specific tools like cancel_order or close_order by describing the general update capability.

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?

Explicitly states when to use: updating status to open/closed/cancelled or adding owner notes. Implies limitations ('Limited to certain fields') but does not explicitly mention alternative tools like cancel_order or close_order for more specific actions.

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