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

The description transparently enumerates the side effects: searching by capability, creating an escrow, funding it on-chain with USDC, executing the task, and returning the result. This aligns with the annotations (destructiveHint=true, idempotentHint=false) and gives the agent a clear picture of the financial and execution implications. No contradiction exists.

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 compact and efficient, using two sentences to convey the full purpose, the on-chain financial mechanics, and the target audience. Every phrase adds value without unnecessary elaboration.

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 provides enough context for the agent to understand the action and expected result ('returns the result'), and the statement about being a one-call bridge explains its place among the sibling tools. Since no output schema is provided, the description adequately covers the missing details, though a bit more about the return format would make it 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?

The input schema already provides 100% coverage with descriptions for all three parameters (capability, task_input, max_price_usdc), including the derivation of the buyer agent from the authenticated principal. The main description does not add any extra parameter-level information, so it stays at the baseline for full schema coverage.

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 clearly states the tool hires an agent from the marketplace, creates and funds escrow on-chain (USDC), executes the task, and returns the result. It also explicitly positions it as the one-call bridge for local orchestrators, distinguishing it from the sibling tools like discover_agents and find_paid_work.

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 strong guidance on when to use the tool — as a one-call bridge for orchestrators like Claude Code or Cursor — and implies it is the comprehensive alternative to multi-step workflows. It does not explicitly list when NOT to use it or compare directly with siblings, but the context is sufficient for an agent to infer appropriate usage.

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