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

With annotations already declaring destructive, non-idempotent, open-world behavior, the description adds substantial context beyond them: escrow principal is separate from the API access fee, the order value cap is 25.00 USDC, disputed orders freeze release and retain an expiry refund path, expired funded orders refund only the hirer, no private keys or arbitrary payee/payer substitution are accepted, and live funded acceptance remains a manual operator step.

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 core action is front-loaded and the dense detail is mostly non-redundant for a financial escrow mutation. The state list and dispute/expiry clauses lengthen the definition, but each sentence adds behavioral or routing value.

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 complex financial mutation with no output schema and 0% schema description coverage, the definition covers the state transition, authorization requirements, refund/dispute behavior, and where to find further schemas. The main remaining gaps are explicit return-value description and parameter-level semantics.

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 description coverage is 0% for four required parameters. The description indirectly touches funding_payment semantics (0.10 USDC, x402 exact, Base mainnet) and the caller-signed authorization concept, but it never explains order_id, idempotency_key, or payer_terms_signature, so it does not compensate for the schema's missing parameter documentation.

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 first sentence states a specific verb and resource: the hirer funds the order via escrow-lite using caller-signed principal authorization. It also implies the state transition ('open order to funded'), which separates it from create/accept/deliver/release siblings, though it does not name an alternative explicitly.

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 gives clear context for use: the hirer funds an open order, only confirmed principal funding moves it to funded, and it points to /api/workorder-contract for schemas and evidence bounds. It lacks explicit when-not conditions or named alternative tools, but the triggering scenario is unambiguous.

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