x402_bazaar_catalog

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

With no annotations, the description carries the full behavioral burden. It adds useful context by stating the tool is free and listing what it returns, which implies a read-only discovery operation, but it does not explicitly disclose side effects, authentication requirements, rate limits, response size, or output format.

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?

It is a single front-loaded sentence that identifies the tool as free discovery and enumerates the returned artifacts without unnecessary wording. Every phrase contributes to explaining what the tool is and what it provides.

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?

For a zero-parameter read-only catalog with no output schema, the description names the key returned artifacts and states that it is free. It could be slightly more complete about response structure or size, but it gives enough information to invoke the tool correctly.

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?

The tool has zero parameters and an empty input schema, so there are no parameter meanings for the description to clarify. The baseline for zero parameters is 4, and the description does not need to compensate for any schema gaps.

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 ('returns') and resource (the Coinbase x402 Bazaar semantic catalog, available verification endpoints, pricing in Base USDC, and schema definitions). It labels itself a discovery tool, which helps distinguish it from the sibling verify_* tools, but it does not explicitly name or contrast those siblings.

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 phrase 'Free discovery tool' implies it is used to discover endpoints, pricing, and schemas rather than to perform verification, and the sibling names suggest that verification belongs to the other tools. However, it provides no explicit when-to-use, when-not-to-use, or named alternative guidance.

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