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

The description carries real behavioral weight beyond the annotations: funds leave the wallet immediately, are held until release, incur a fee, and come back only if nothing is submitted before release_deadline, plus a feature_unavailable failure mode. However, the key money and deadline semantics (immediate debit, escrow hold, fee on release, refund window) are not spelled out here; that omission is material for a tool that moves funds, so the description does not fully own its behavioral burden even with destructiveHint=false.

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 plus a short error note, front-loaded with purpose and then behavior. The parameter enumeration in the first sentence partly restates the schema, but it is compact and each clause carries information.

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 10-parameter, nested-schema, no-output-schema tool, the description covers intent, money flow, and the disabled-state error but says nothing about the input_covered and spot_check exclusions noted in the schema, or about how subsequent actions work (release_escrow, refund_escrow, dispute_escrow). See the following summary for the overall assessment.

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 description adds meaning the schema lacks, notably that external_id is 'the job on that platform' and that amount is USD, while flagging acceptance_tests and auto_release as optional. With schema coverage at 70% and nested acceptance_tests config largely self-documenting, this compensates for most remaining gaps.

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 opens with a specific verb and resource ('Pay another agent through escrow') and immediately scopes it to 'work arranged elsewhere', which separates it from the on-platform task flow (post_task / submit_to_escrow). An agent can tell what this tool does and what it does not do without opening another schema.

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?

It gives a clear selection rule ('for work arranged elsewhere') plus the lifecycle that follows a call: funds held, released later, or refunded at the deadline. It never names an explicit alternative tool or a when-not-to-use case, so the agent must infer that on-platform work belongs in post_task.

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