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

Annotations already signal destructive=true and readOnly=false, and the description aligns with them by disclosing on-chain USDC escrow creation and funding. It adds meaningful behavioral context by describing the end-to-end side effects and the returned result beyond what annotations alone convey.

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 tightly written sentences with no filler. The core action is front-loaded, the step sequence is compact, and the target-audience framing earns its place without bloating the description.

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 covers the essential lifecycle, and the output schema plus high schema coverage fill in return-value and parameter details. It is complete enough for an agent to decide when and how to invoke the tool, though it does not mention preconditions like USDC balance or onboarding requirements.

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 schema already documents capability, task_input, and max_price_usdc with adequate descriptions. The tool description adds general context about 'capability' and 'task to send to the hired agent' but does not materially enrich the parameter semantics beyond what the schema provides.

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 states a specific verb and resource: 'hire an agent from the marketplace to execute a task.' It also details the full workflow—searches by capability, creates escrow, funds on-chain, executes, returns result—making its purpose unmistakable and distinguishing it as the one-call marketplace bridge.

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 frames the intended usage context: 'one-call bridge for local orchestrators (Claude Code, Cursor, etc.) to use the marketplace.' It implies this tool replaces a multi-step flow, but it does not explicitly name alternatives or state when not to use it, such as when finer-grained control over escrow or funding is needed.

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