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

With no annotations provided, the description carries the burden of behavioral disclosure. It discloses the $0.10 per-call price, x402 payment method, and Base mainnet USDC, and clearly implies a read-only monitoring operation through 'check', 'pulse', and 'where do I rank now'. It does not detail rate limits or authentication, but for a low-cost read-like check the key traits are covered.

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 front-loaded with the core purpose and output, and the subsequent sentences add useful usage and pricing context. The rhetorical questions ('Where do I rank now? Am I being out-ranked?') add a slightly promotional tone but do not waste significant space; overall it is appropriately sized for a simple tool.

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?

Despite lacking an output schema and annotations, the description explains the output composition (best rank + per-category-keyword rank) and the fallback to the visibility audit. For a single-parameter read-only check, this is largely complete; minor gaps remain on exact response format or rank definition, but the description covers the essential context.

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% for the single 'seller' parameter, which already documents wallet or origin URL/domain formats. The description adds context about the seller being an x402 seller in CDP Bazaar, but does not materially extend parameter semantics beyond the schema; hence 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?

The description clearly states a specific action: checking an x402 seller's current keyword-relevance rank in CDP Bazaar discovery. It distinguishes this from raw settled-volume rank shown by free explorers and from the sibling tool 'agent_visibility_audit', making its unique purpose evident.

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 frames this as a frequent pulse/cheap monitoring call, and explicitly points to the full '/agent/visibility-audit' when rank slips, naming the alternative. It also contrasts with free volume-rank explorers, providing clear when-to-use vs when-not-to guidance.

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