hire_agent

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It explains payment mechanism (USDC via x402 with escrow + verification, only pay if output passes verification), synchronous execution, and the dual semantics of max_price_usdc (free-hire vs cap intent). No contradictions with any 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?

The description is longer than average but well-structured with a clear summary sentence followed by detailed bullet points for the two max_price_usdc patterns. It is front-loaded with the core purpose and usage instructions. Each sentence adds value, though minor trimming could improve conciseness.

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 5 parameters and no output schema, the description covers inputs thoroughly, including required parameters and optional ones like max_latency_ms. It mentions the result is synchronous but does not specify the output format. It also notes prerequisites (wallet). Overall, it is complete enough for the tool's complexity.

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 all parameters. However, the description adds significant value by explaining the two patterns for max_price_usdc in detail, which is not in the schema description. For other parameters like capability and params, the description does not add much beyond the schema.

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 clearly states the tool's purpose: 'Hire an agent to execute a capability. Returns the result synchronously.' It uses a specific verb ('hire') and resource ('agent'), and distinguishes itself from siblings like search_agents and get_agent_id by focusing on the hiring action.

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 explicit when-to-use guidance: 'Use this after you've found a suitable agent via search_agents (or pass agent_id=null to auto-pick the best match). Requires a wallet.' It also details two valid patterns for max_price_usdc, clarifying when to use free-hire intent versus cap intent, and warns about critical behavior changes in SDK versions.

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