create-fulfillment

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

With no annotations, the description carries the burden, and it does add the key behavioral fact that this marks items as shipped (a state change) and that IDs must be pre-fetched. However, it omits reversibility, partial-fulfillment implications, and permission requirements; the notifyCustomer warning lives in the schema, not the description.

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?

Two tight sentences: the action first, then the critical prerequisite flagged with IMPORTANT. Zero filler.

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 nested, mutating tool with no annotations and no output schema, the description covers purpose and ID sourcing but says nothing about the result (fulfillment status returned), error/partial-success behavior, or that fulfilling all line items is the default when the line item array is omitted. The rich schema compensates for field-level gaps but not for outcome expectations.

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 explains every field, giving a baseline of 3. The description adds value by highlighting that fulfillmentOrderId and line item GIDs come from get-fulfillment-orders, which is the most error-prone part of the call.

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?

States a specific verb and resource ("Create a fulfillment") and clarifies the business effect with "mark items as shipped", so the agent knows exactly what happens. It names the prerequisite sibling get-fulfillment-orders, giving partial differentiation, though it doesn't contrast with other order-mutation tools like order-mark-as-paid.

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 prescribes the workflow: call get-fulfillment-orders first to obtain IDs. That is a concrete usage condition rather than an implied one. It does not state when NOT to use this tool (e.g., cancellations or refunds), which keeps it below a 5.

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