Send the purchase order (step 2 of 2)

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

Annotations already indicate the operation is not read-only and is destructive/idempotent. The description adds useful behavioral context: the token expires in 5 minutes and the call must follow explicit user confirmation, which clarifies the irreversible nature implied by destructiveHint.

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 sentences, no filler. The primary action is stated first, then the prerequisite and timing constraint, then the user-confirmation requirement. 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?

With a single parameter, a clear prerequisite, expiration semantics, explicit user-confirmation condition, and an output schema present, the description covers everything needed to invoke this correctly alongside its sibling tools.

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 schema only provides the token's type and length, with 0% description coverage. The description compensates by explaining that confirmation_token comes from create_purchase_order_draft and expires after 5 minutes, giving the parameter meaningful operational context.

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 ('Sends') with a clear resource ('drafted purchase order') and even cites the endpoint (POST /purchaseorders). The title explicitly labels it 'step 2 of 2', distinguishing it from create_purchase_order_draft.

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 states when to call it ('only after the user explicitly confirms'), what prerequisite is required (confirmation_token from create_purchase_order_draft), and adds a time constraint (expires after 5 minutes). This gives an agent actionable go/no-go conditions.

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