Confirm delivery and release escrow

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

With no annotations provided, the description carries the full burden. It discloses the financial side effect (releasing escrow), the required state, and a time-based fallback behavior. This is rich, honest disclosure of what calling the tool does and its consequences.

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 tightly written sentences, each earning its place: the action and effect, the precondition and urgency, and the fallback behavior. Nothing is wasted or repetitive.

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 tool with no output schema, the description is complete: it explains the purpose, the required state, the urgency, and the risk of non-action. No critical information missing.

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 has 100% coverage for the only parameter (orderId) with its type and format. The description adds no additional meaning beyond the schema, so the baseline of 3 is appropriate.

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 states a specific verb ('Confirms'), clear object ('goods or digital content'), and direct outcome ('releases the escrowed funds to the seller'). It clearly distinguishes itself from siblings like cancel_order and get_order by focusing on the confirmation-and-payout action.

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?

Provides explicit when-to-use guidance ('Call promptly once delivery is verified') and a precondition ('Requires the order's escrowStatus to be Shipped'). It also warns about the auto-finalise timer as a fallback, implicitly guiding the agent to act quickly rather than wait.

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