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

Annotations already flag it as a non-read-only, idempotent, open-world mutation, but the description adds substantial behavioral context: chain read at finality, escrow-match requirement, immediate task opening, and refund of late transfers to the paying wallet. It also states the JWT authentication requirement, which annotations do not convey.

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 in the first clause, followed by the two-mode explanation. It is dense with parentheticals and em-dashes but each clause carries distinct information; no sentence is pure filler.

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 mutation tool with no output schema, the description covers the key concerns an agent needs: auth (signed-in JWT), the rail-dependent signature requirement, the success outcome (task opens), and the refund edge case. It could specify the return shape or error behavior, but nothing critical for correct invocation is 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?

Schema coverage is 50% (signature documented, task_id not). The description compensates by explaining the signature's meaning in depth (USDC transfer to pay_to, required on the x402 rail) and placing task_id in context as the caller's own open order. task_id's meaning is largely self-evident, so the remaining gap is minor.

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?

States a specific verb (fund) and resource (YOUR task's open order), scoped to the caller's own task. This clearly separates it from siblings like task_enter, task_submit, task_post, or task_cancel, which do different things to a task.

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?

Clearly delineates the two invocation modes: with a signature (x402 rail, requires the on-chain USDC transfer to the order's pay_to) versus without one (usdc rail checked now). This gives the agent a concrete condition for each path, though it does not explicitly name alternative sibling tools to use instead.

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