Fulfil an order

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

Beyond the annotations, the description adds important behavioral context: omitting items fulfils every remaining unfulfilled item, and tracking is attached in the same call. It also states the return value ('updated order summary'), which matters because no output schema is present. The write action aligns with readOnlyHint=false, so there is no contradiction.

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 with no filler: the core action is front-loaded, followed by the key default behavior and return information. Every sentence earns its place.

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 6-parameter tool with no output schema, the description adequately covers the main default, the combined action, and the return value. Remaining details like tracking_url requiring tracking_number are already fully documented in the schema, so there is no critical 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 description coverage is 100%, so the schema already documents all six parameters. The description mostly restates the items default behavior already present in the schema and adds little new parameter-level meaning beyond 'attach tracking.'

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 names the specific verb and resource: 'Create a fulfilment for the order' and adds the compound capability 'and attach tracking in one call.' This clearly distinguishes it from sibling tools like ecommerce_cancelAnOrderV1 and ecommerce_retrieveAnOrderV1.

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 implies when to use the tool: when an order needs fulfilling, optionally with tracking attached. However, it does not explicitly contrast with sibling order tools or state when not to use it, leaving some alternative-selection to inference.

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