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

The description discloses consequential behavior beyond what annotations provide: it creates an escrow, funds it on-chain with USDC, and executes the task. This makes the financial and side-effecting nature explicit and is consistent with destructiveHint=true and idempotentHint=false. It does not cover failure/refund behavior or authorization requirements, but the annotations and output schema reduce the burden.

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 front-loads the action and then describes the workflow in a compact sequence; the second adds valuable positioning about the intended callers. Every sentence 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?

For a complex, side-effecting tool, the description covers the entire pipeline, the on-chain USDC funding, and the result return. Annotations and the output schema cover safety and return shape. The only notable gap is that the description does not explicitly warn about cost or irreversibility, though 'funds the escrow on-chain (USDC)' makes the financial nature clear enough.

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 capability, task_input, and max_price_usdc are already documented in the input schema. The description reinforces the capability-search and USDC-funding concepts but adds no parameter-level detail beyond what the schema provides. The baseline of 3 applies because the schema carries the parameter documentation burden.

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 opens with a specific verb and resource: 'Hire an agent from the marketplace to execute a task.' It then enumerates the full pipeline—search by capability, create escrow, fund on-chain in USDC, execute, return result—which makes the tool's purpose unmistakable. The final sentence positions it as the one-call bridge for local orchestrators, clearly distinguishing it from narrower marketplace tools like discover_agents or get_agent_contract.

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 that this is the one-call bridge for local orchestrators such as Claude Code and Cursor, implying it should be used when a caller wants the entire hire-and-execute flow in a single call. It does not explicitly name alternatives or exclusion conditions, such as 'use discover_agents if you only want to search capabilities,' so it stops just short of full when/when-not guidance.

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