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

Adds substantial behavior beyond the readOnly/openWorld annotations: it discloses the index is third-party (Coinbase CDP), that the call is free and requires no payment, and precisely defines the derived "payable" flag (USDG on Robinhood Chain, USDC on Solana/Base/Arbitrum/Polygon). That payable criterion is exactly the kind of non-obvious detail an agent needs to interpret results.

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?

Roughly four sentences, each doing distinct work: what it searches, what it returns, when to use it, and its cost. The scope constraint and usage rule are front-loaded with no filler.

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?

Although no output schema exists, the description enumerates the returned fields (URL, method, price, networks, example input, payable flag), so an agent knows what it will get back. Combined with the cost and routing info, nothing needed to call it correctly is missing.

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%, and the schema already documents both query (with examples) and limit (default 10, max 20). The description adds no parameter-level detail such as query syntax or result-paging guidance, so baseline 3 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?

States a specific verb and resource — searching the x402 Bazaar index run by Coinbase CDP — and explicitly scopes it to APIs "outside Wafermap's own catalog." That contrast with the internal catalog siblings (wafermap_resources, wafermap_tokens) lets an agent distinguish it without opening a schema.

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 an explicit routing rule: "Use it when no Wafermap resource fits the task," with the corollary that Wafermap's own catalog is the first stop. Naming categories of what it finds (weather, web search, data enrichment, token prices) further helps an agent judge fit.

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