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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses ranking behavior (task relevance plus bounded source-reported activity), the non-influence of paid Ontario publication on ranking, and the important caveat that the tool is not a safety certification. It also notes the search is free, providing cost semantics.

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 dense but efficient: the primary function is front-loaded, and every clause adds useful context (ranking criteria, budget filtering, safety caveat, provider-side routing). It could be slightly more readable due to heavy jargon, but there is no filler or repetition.

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 output schema exists and annotations cover safety, the description provides the complete operational context an agent needs: what the tool searches, how rankings work, cost implications, non-certification warning, and explicit routing to alternative workflows. No critical selection or invocation information 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%, so the schema already fully documents all five parameters. The description adds only light context such as 'Base/USDC budget filtering' mapping to network and max_usdc, but does not significantly enhance parameter understanding beyond the schema, yielding the baseline score of 3.

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 action ('free buyer-side search'), names the concrete resources searched ('Ontario's fresh strict-ready paid profiles, Agentic Market, and Coinbase CDP Bazaar'), and distinguishes the tool from provider-side publication workflows. It also clarifies the tool's nature as discovery rather than certification, leaving no ambiguity about what it does.

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 explicitly says when to use this tool ('buyer-side search') and when not to ('provider-side publication intent'), and instructs to skip the marketplace search and instead return the listing validator and publication workflow. It also directs users to run readiness and can-pay checks before spending, mapping to sibling tools x402_readiness_verify and agent_can_pay.

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