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

The description discloses the concrete behavioral sequence: searching by capability, creating escrow, funding it on-chain in USDC, executing, and returning results. This adds meaningful process context beyond the annotations' readOnly=false/destructive=true hints, though it could further emphasize irreversibility/cost implications.

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?

Three sentences, no filler; the main action is front-loaded, the process pipeline is compact, and the target audience is established in one final sentence. Every sentence earns its place.

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?

The description captures the purpose, process, target users, and result for a complex multi-step operation, and an output schema exists so return-value detail is unnecessary. The authenticated-principal behavior is already covered by the input schema's description, and the monetary side effect is surfaced through 'funds the escrow on-chain (USDC)' plus the max_price_usdc parameter.

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 100%, so the structured schema already documents capability, task_input, and max_price_usdc. The tool description adds only light context such as 'searches by capability' and 'USDC,' which is useful but not a substantial supplement beyond the schema.

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?

Description opens with a specific verb and resource ('Hire an agent from the marketplace to execute a task') and then details the full pipeline: search, escrow creation, on-chain USDC funding, execution, and result return. It also positions itself as the one-call bridge, which distinguishes it from multi-step marketplace operations like data_session_fund and data_session_attach_escrow.

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 clearly states this is the one-call path for local orchestrators, giving an explicit target audience and integration context. It does not explicitly name alternative tools or describe when not to use it, but the 'one-call bridge' framing implies it should be chosen over composing the separate escrow/fund/execute steps.

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