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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description aligns by explicitly revealing that the tool funds an escrow on-chain with USDC, which implies financial movement and irreversible side effects. It also adds useful context that the buyer agent is derived from the authenticated principal, not from arguments. No contradiction with 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 is two sentences with no filler. The first sentence front-loads the core action and the key side effect (on-chain funding), and the second sentence situates the tool for its target audience. Every sentence contributes essential 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?

Given the tool's complexity—financial side effects, marketplace search, escrow creation, and execution—the description covers the full lifecycle in a compact way. The output schema exists, so return-value details are not required. A minor gap is that it does not warn about irreversibility or potential cost beyond 'funds the escrow,' but the destructive annotation and explicit USDC funding mitigate this.

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 100%, so the baseline is 3, but the description adds meaningful context beyond the schema: only capability, task, and price ceiling 'travel' in the call, and the buyer identity is derived from authentication. This clarifies the role of max_price_usdc as a ceiling and reinforces that no agent identity parameter should be supplied.

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 action ('Hire an agent from the marketplace to execute a task') and details the full pipeline: search, escrow creation, on-chain USDC funding, execution, and result return. It explicitly brands itself as the 'one-call bridge' for local orchestrators, which clearly distinguishes 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 defines the intended context: local orchestrators such as Claude Code and Cursor needing a single call into the marketplace. It implies the alternative is a manual multi-step flow, though it does not explicitly name sibling tools or state when not to use it. Still, the 'one-call bridge' positioning gives an agent clear situational guidance.

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