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

Beyond the annotations, the description discloses the meaningful behavioral steps: creating escrow, funding it on-chain in USDC, executing the task, and returning the result. This is substantial context for a tool that moves money. It does not cover failure/refund behavior, but the annotations already flag it as destructive and not read-only.

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 three focused sentences: it states the action, gives the end-to-end flow, and names the audience. Every sentence 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 rich parameter schemas, output schema, and annotations, the description is sufficiently complete for an agent to understand what will happen when invoking this tool. It covers the purpose, the funding mechanism, the execution flow, and the return of results with no critical gaps.

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 parameters are already well-documented. The tool description only echoes the concepts of capability, task, and price ceiling without adding parameter-level detail. It does not go beyond what the input schema already provides, so a baseline score is appropriate.

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 clear verb and resource: 'Hire an agent from the marketplace to execute a task.' It then spells out the full pipeline—searches by capability, creates escrow, funds on-chain USDC, executes, returns result—making the purpose unmistakable. It also distinguishes itself as the one-call bridge, separating it from related marketplace/sibling tools.

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 the intended audience and use case: 'one-call bridge for local orchestrators (Claude Code, Cursor, etc.) to use the marketplace.' This gives strong contextual guidance on when to choose it. It stops short of explicitly naming alternatives or saying when not to use it, but the positioning is clear enough.

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