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

The annotations already indicate this is not read-only, is destructive, and is not idempotent. The description adds meaningful behavioral context by disclosing that it creates an escrow, funds it on-chain with USDC, and returns the result, which informs the agent that calling this tool has real financial side effects beyond a typical API call.

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 is two sentences with no filler: the first sentence front-loads the core action and pipeline, and the second establishes the target audience and bridge role. Every clause 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?

Given the tool's complexity, the description covers the essential flow, the on-chain funding side effect, and the return of results. An output schema exists and all parameters are fully described, so the description does not need to explain return structures. A brief mention of prerequisites or explicit alternatives would make it fully complete.

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 baseline is 3. The tool description does not add parameter-level meaning, but the schema already covers capability, task_input, max_price_usdc, the default of '1.0', and the validation pattern. No compensation is needed.

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 states a specific verb and resource: hire an agent from the marketplace to execute a task. It goes further by enumerating the multi-step flow (search, escrow, USDC funding, execution, result) and by positioning itself as the 'one-call bridge' for local orchestrators, which clearly differentiates it from multi-step sibling tools like data_session_attach_escrow and data_session_fund.

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 when to use this tool: when a local orchestrator wants a single-call bridge to the marketplace. It does not explicitly list exclusions or name alternative tools for cases like inspecting agents first or funding separately, so it stops just short of full when-not guidance.

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