firestarter_confirm_order

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

Annotations provide readOnlyHint=false and destructiveHint=false, so mutation is already known. The description adds behavioral context: confirming 'notifies the buyer that the order is accepted' and 'is the gate before shipping,' plus the precondition that the order must be pending. No contradictions.

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 around 120 words and includes essential info: action, flow position, when to use, parameter caveat, and state precondition. Every sentence contributes; it's compact but not overly terse.

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 single-parameter mutation tool with no output schema, the description covers purpose, usage context, parameter semantics, and valid state precondition. It explains what happens (buyer notified) and where it fits in the overall flow, making it complete for an agent.

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?

Input schema already fully describes order_id with 100% coverage, including the distinction from exec_... execution id. The description repeats this warning ('the order_id field, NOT the exec_... execution id') but adds no new semantic meaning beyond emphasis.

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?

Description opens with 'Accept a pending incoming order' and explicitly positions it as 'step 2 of the seller fulfillment flow' with the chain firestarter_seller_orders → firestarter_confirm_order → firestarter_ship_order, clearly distinguishing it from sibling tools like firestarter_ship_order and firestarter_seller_orders.

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 'Use when a seller wants to accept/confirm an order a buyer placed' and provides exclusion criteria: 'Only orders still in pending can be confirmed' and directs users to 'go straight to firestarter_ship_order' for already confirmed/shipped orders.

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