firestarter_ship_order

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses important side effects: the buyer is automatically notified and can track delivery, and no separate buyer message is needed. It also reveals the carrier default behavior (USPS). This adds meaningful behavioral context for a mutation tool.

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 cover the action, flow context, trigger condition, required/optional params, and a common pitfall. Each sentence carries information; no redundancy or 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?

Given the lack of an output schema and the mutation nature, the description sufficiently covers what to expect: the order is marked shipped, buyer is notified, and tracking is enabled. It also places the tool in the broader fulfillment workflow. It omits a description of the return value, but that is rarely critical for a confirmation action.

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 input schema already documents all three parameters with descriptions, so baseline is 3. The description reinforces the critical distinction between order_id and exec_... id and reiterates the carrier default, but does not introduce new parameter semantics beyond the schema. Still, it provides practical guidance for passing order_id correctly.

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 uses a specific verb ('Mark an order shipped') and identifies the resource (order) and the required data (carrier and tracking number). It clearly positions this as the final step in the seller fulfillment flow, distinguishing it from upstream steps like firestarter_confirm_order.

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 states when to call ('once the seller has actually handed the package to the carrier and has a tracking number') and provides the sequential context (firestarter_seller_orders → firestarter_confirm_order → firestarter_ship_order). It also clarifies required vs optional params and warns against using the exec_... id, which is actionable guidance for correct invocation.

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