update_store_order

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

Beyond annotations, the description discloses authentication via API key, max 10 concurrent requests, and respect for read-only and dry-run modes. No contradictions with annotations. It does not detail all side effects, but the behavior is well-covered.

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?

The description is concise and well-structured: main action first, then details in Args/Returns format. Every sentence adds value, and the length is appropriate for the tool's complexity.

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 4 parameters, output schema, and annotations, the description is complete. It covers purpose, usage, parameters, behavior (auth, concurrency, modes), and references for obtaining inputs. No gaps identified.

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 explains all parameters with examples and guidance (store_id from list_ecommerce_stores, additional_fields with e.g. values, account with environment variable naming). This compensates for the schema's lack of descriptions (0% coverage).

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 tool updates an existing e-commerce order's fields, with specific details about partial updates (only passed fields are changed). It distinguishes from create/delete order tools and mentions integration types.

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 explains when to use this tool (manual commerce for custom/headless stores) and when it's not needed (Shopify/WooCommerce sync automatically). It does not explicitly mention alternatives like create or delete, but the context is clear.

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