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

The description discloses the full side-effect chain: searching, creating escrow, funding on-chain with USDC, executing the task, and returning the result. This adds valuable context beyond the annotations' destructiveHint and idempotentHint, especially the on-chain financial impact. It does not contradict 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?

Two sentences with no filler. The first sentence states the core purpose, and the second gives the essential execution flow and intended audience. Every clause contributes value.

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?

With an output schema present, full schema description coverage, and annotations covering risk traits, the description is largely complete. It explains the end-to-end behavior and return expectation. A slightly fuller warning about failure/refund behavior or the irreversible on-chain funding would push it to a 5, but the current schema and annotations already carry much of that weight.

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 description mentions 'capability' and 'task' conceptually but adds no parameter-specific detail beyond the schema. The schema itself already documents capability, task_input, and max_price_usdc, including the notable principal-derived buyer behavior.

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 names a specific action ('Hire an agent from the marketplace to execute a task') and gives a concrete process: search by capability, create escrow, fund on-chain, execute, return result. It also distinguishes itself from siblings by calling itself the 'one-call bridge for local orchestrators' to use the marketplace.

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 the intended context: local orchestrators such as Claude Code or Cursor wanting a single call to hire and execute. It implies this is the all-in-one alternative to multi-step marketplace flows, though it does not explicitly name sibling tools to avoid or list exclusion criteria.

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