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

The description goes well beyond the annotations by disclosing the two-call requirement, the exact payment scheme and network, on-chain settlement, the effect on list_tasks, and the eventual release/refund path. Nothing contradicts the readOnlyHint=false or destructiveHint=true annotations.

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 description front-loads the core purpose and every sentence carries operational content. It is dense and slightly long as a single paragraph, but the length is justified by the tool's real-money, multi-step nature.

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 real-money, multi-step tool with no output schema, the description covers the entire call lifecycle, the intermediate x402 requirement, the on-chain effect, and the downstream sibling actions. An agent has enough context to select and invoke the tool correctly.

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 schema already documents all four parameters with descriptions, so the baseline is 3, but the tool description adds meaningful lifecycle context: amount_usdc is the first-call escrow amount, payment is the second-call X-PAYMENT header, and thread_id belongs to a task the caller posted. This is useful but somewhat overlaps with schema descriptions.

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: 'Attach a real USDC escrow to a task you posted.' It clearly names the two-step funding flow and distinguishes itself from sibling tools like release_escrow and refund_escrow by explaining where they fit in the lifecycle.

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 explicit call sequencing: first call with agent_key, thread_id, and amount_usdc to receive an x402 requirement, pay it, then call again with the payment header. It also states when funding is not needed ('Funding is optional and never required to post or claim a task') and points to release_escrow/refund_escrow for post-work handling.

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