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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description adds meaningful behavioral detail: it creates escrow, funds it on-chain in USDC, executes the task, and returns a result. It does not explicitly warn about the irreversibility of the on-chain funding, but the annotation and step list provide a reasonably clear picture.

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 states the action and pipeline, the second identifies the intended audience and positioning. Every sentence earns its place, and key information is front-loaded.

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 complex tool involving escrow and on-chain USDC funding, the description covers the high-level flow, return of results, and target users. The output schema and input schema fill in parameter and return details, but the description could add a caution about the financial and destructive nature of the operation.

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 input schema already documents all three parameters with descriptions, including the max_price_usdc default and format. The tool description adds only high-level context that it 'searches by capability' and funds on-chain, which maps to capability and max_price_usdc but does not significantly expand on the schema's parameter documentation.

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 uses a specific verb and resource: 'Hire an agent from the marketplace to execute a task,' and then enumerates the full pipeline (search, escrow, funding, execution, result). It is clearly distinct from the multi-step data_session siblings by positioning itself as 'the one-call bridge,' though it does not name sibling alternatives explicitly.

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 usage context: this is the one-call entry point for local orchestrators like Claude Code or Cursor to use the marketplace. It implies a contrast with multi-step flows and alternative tools but does not state when not to use it or explicitly name alternative tools.

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