delete_store_order_line

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

Annotations already declare destructiveHint=true and idempotentHint=true. The description reinforces the destructive nature (cannot be undone) but does not clarify idempotency, leaving ambiguity about repeated calls. It adds value by describing the return format but overall does not significantly surpass annotation hints.

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, with an opening sentence summarizing the action, followed by context and an Args section. Every sentence adds value, though the extra context on store types could be seen as slightly tangential.

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 (delete operation), the description covers the main aspects: what it does, permanence, return values, and source for store_id. However, it lacks details on optional parameters, prerequisites, and behavior on repeated deletion, which would enhance completeness.

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 lists three of the four parameters (store_id, order_id, line_id) with brief explanations, such as obtaining store_id from list_ecommerce_stores. However, it fails to mention the optional 'account' parameter, and with 0% schema coverage, this omission is notable.

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 it permanently deletes a line item from an e-commerce order, distinguishing it from deleting the entire order or store. It also mentions that for Shopify/WooCommerce, order lines are synced automatically, implying this tool is for manual/custom stores.

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?

It explicitly says manual commerce writes suit custom/headless stores, and that Shopify/WooCommerce integrations sync order lines automatically, providing clear context on when to use this tool versus alternatives. However, it does not explicitly compare to sibling delete tools like delete_store_order.

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