shopify_create_fulfillment

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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds meaningful operational context: dryRun defaults to true (a safe preview), notifyCustomer defaults to false, which scopes are required, and that Shopify may report additional missing scopes for fulfillment-service orders. It does not fully explain reversibility or side effects, but it adds real value beyond the annotations.

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, front-loaded with the core action and scope, with auth and default behaviors following. No filler, though the tracking-parameter cluster is glossed rather than explained.

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 destructive mutation with no output schema, the description covers the essential operational details: dryRun default (with the note that preview is non-mutating and false applies and reads back), notifyCustomer default, and required scopes. It stops short of documenting the individual tracking parameters, which is the main remaining gap.

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 only 14%, so the description carries most of the burden, yet it only generically references 'optional tracking' and restates defaults (notifyCustomer, dryRun) that the schema already declares. store, orderId, trackingUrl, trackingNumber, and trackingCompany get no semantic help, leaving key parameters under-specified.

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 states a specific verb (fulfill) and resource (an order's fulfillment orders), and even narrows the scope to remaining quantities of OPEN and IN_PROGRESS orders. It is clearly distinguishable from generic mutation siblings, though it does not explicitly name an alternative tool.

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?

Usage context is implied by 'fulfill the remaining quantities' and the note about which fulfillment orders are eligible, plus required scopes. However, there is no explicit when-to-use vs when-not guidance and no named alternative among the many sibling tools.

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