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

The description discloses the side-effect sequence beyond the annotations: it creates escrow, funds it on-chain with USDC, executes the task, and returns a result. This is valuable because it signals a paid, multi-step, externally visible transaction. It does not mention non-refundability or failure modes, but the annotations already flag destructive and non-idempotent behavior, lowering the bar.

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 dense sentences with no filler, front-loaded with the core action and resource. Every clause adds useful information: the search mechanism, escrow creation, on-chain funding, execution, result return, and target audience.

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 money-moving marketplace bridge, the description plus the schema-level authentication note cover the essential context an agent needs: capability, task, price ceiling, and principal-derived buyer identity. It lacks explicit caveats about fund non-refundability or execution timing, but the output schema and destructive/non-idempotent annotations fill part of that gap.

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 description does not need to document parameters. The schema already explains capability, task_input, and max_price_usdc, and the schema-level note clarifies that the buyer agent comes from the authenticated principal, never from arguments. The tool description itself adds no additional parameter-level meaning, so it lands at the coverage-based baseline of 3.

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 itemizes the full pipeline: search by capability, create escrow, fund on-chain USDC, execute, and return the result. It also distinguishes itself as the 'one-call bridge' for local orchestrators, setting it apart from single-purpose sibling tools like discover_agents or verify_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?

It gives a clear usage context: local orchestrators (Claude Code, Cursor, etc.) that need the entire marketplace hire-and-execute flow in one call. It does not explicitly name alternatives or state when not to use this tool, so it falls just short of a 5.

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