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

Beyond the annotations (readOnly=false, destructive=true, openWorld=true), the description discloses specific side effects: creating escrow, funding it on-chain in USDC, and executing the task. This gives an agent concrete knowledge of the financial and state-changing behaviors involved, which is exactly the kind of context annotations alone cannot convey. No contradiction with annotations is present.

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 primary action, the second walks through the sequence of effects and closes with the 'one-call bridge' positioning. Every clause earns its place, and the most important 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?

Given the tool's complexity, the description covers the core flow concisely, and the presence of an output schema plus annotations reduces the need to detail return values or safety traits. It lacks explicit prerequisites such as requiring the caller to own an agent or have USDC balance, though the schema's root description partially addresses the agent ownership. Overall, the description is adequate but could add one sentence about prerequisites or the multi-step alternative to be fully 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?

Schema description coverage is 100%, with each parameter (capability, task_input, max_price_usdc) already documented, and the root schema description adds essential context about the buyer agent being derived from the principal. The main description mentions capability and USDC but adds no new parameter-level semantics beyond what the schema already states. Baseline 3 applies because the schema does the heavy lifting.

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 ('Hire') and resource ('an agent from the marketplace'), then details the complete pipeline: search, escrow creation, on-chain USDC funding, execution, and result return. It also explicitly frames itself as a 'one-call bridge' for local orchestrators, clearly distinguishing it from lower-level sibling tools like data_session_fund or discover_agents.

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 provides clear context about when to use this tool: as the single-call entry point for local orchestrators, implying it bundles steps that might otherwise be done via multiple sibling tools. However, it does not explicitly name alternatives or state when not to use it, so it stops 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.