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

Annotations already declare destructive=true and idempotent=true, but the description adds genuinely useful context beyond them: acceptance unlocks seller payout eligibility, dispute freezes release, and a server-side payout flag must be enabled for an actual transfer. That precondition is real behavioral disclosure an agent could not derive from the annotations. It stops short of 5 because it says nothing about permissions or authorization.

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, front-loaded with the outcome the agent cares about and followed by the caveat. No filler or redundancy.

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?

An output schema exists, so return values need not be explained, and the annotations cover the safety profile. The description supplies the key precondition and consequence, making it nearly complete; the only gap is guidance on when to invoke it relative to sibling trade 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?

Schema coverage is 100%, so the schema already documents order_id, accepted, and note in detail. The description's mapping of acceptance to payout eligibility and dispute to frozen release adds marginal meaning over the schema, but no syntax or format detail. Baseline 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 name and title state a specific verb+resource (accept or dispute delivery), and the description reinforces it by naming the buyer-side consequence (payout eligibility vs. frozen release). It implicitly distinguishes from the seller-side nexus_trade_deliver_order, though it never names that sibling. The description itself describes effects rather than the action, so a 4 rather than 5.

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?

Usage is only implied: the description frames this as the buyer acceptance step ('Buyer acceptance...'), from which an agent can infer it follows a delivery. There is no explicit when-to-use, when-not-to-use, or routing to alternatives such as nexus_trade_deliver_order or nexus_trade_settlement_status.

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