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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=true), yet the description adds critical behavior they cannot express: the per-call price ($0.03 USDC), accepted payment rails (x402 or prepaid credits), and that usage is currently inside a free trial. It also discloses the shape of the work performed (catalogue search, AI comparison, top-3 return), so the agent knows this is a paid, non-trivial lookup rather than a cheap local query.

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 purpose and the payoff sentence are front-loaded, followed by an example and pricing; the sentences are dense and informative. It runs slightly long with the trailing pricing/trial sentence, but nothing is redundant with the schema or annotations.

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 an output schema exists, return values need not be explained, yet the description still sketches the response (top 3 with reasons and a callable URL). Inputs, cost, payment method, and trial status are all covered, which is everything an agent needs to decide to call it.

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% — task, network, and maxPrice all carry their own descriptions with bounds and formats. The description adds only an illustrative example of the 'task' string and no semantics for network or maxPrice, so it does not meaningfully exceed the schema baseline.

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?

States a specific verb and resource: describes a job, searches the Bazaar catalogue, has an AI compare candidates and returns the top 3 with reasons and the exact URL to call. The mechanism is spelled out in detail, so the agent knows exactly what it gets. It does not, however, name the overlapping siblings (x402-find, x402-find-live, find-best-tool), so differentiation is left to inference.

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?

Provides a concrete use example ('check if a Base token is a rug pull') and a rationale for using it ('saves agents trial-and-error payments'), which implies when to reach for it. But with three near-synonymous x402/finder siblings available, it never states when NOT to use this tool or which alternative to pick, so the routing guidance is only implied.

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