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

With no annotations, the description carries the burden and does disclose the critical behavioral trait: it is a paid call (0.0050 USDC on Base mainnet via x402), plus the output scope shrinkage under lite:true and the 30-minute snapshot cadence. It omits failure modes, latency/timeout expectations, and retry behavior for the payment flow.

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 value is front-loaded ('The x402 agent economy in one call') and the differentiating sentence plus payment note land before the parenthetical detail. It is a single dense sentence whose embedded statistics (28K+, 1886 hosts, 24h/7d/30d) are informative rather than padding, though the length is at the upper end.

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?

With no output schema and no annotations, the description must carry the full load, and it enumerates the returned data sets, the lite-mode variant, the snapshot cadence, and the payment requirement. Nothing an agent needs to decide to call it or to interpret the response 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 coverage is 100% and there is only one optional boolean, so the schema already fully documents 'lite'. The description's 'Set lite:true for market vitals + top 5 merchants' largely restates the schema's own wording rather than adding new semantics, landing at the baseline 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 names a specific verb scope ('in one call') plus the exact resource set: PayAI Bazaar market vitals, top-20 merchants, trend history, and catalog position. It also explicitly differentiates itself from every sibling by stating it is 'the only tool on this server about the MARKET rather than about your endpoint.' An agent can distinguish it from world_status, world_catalog, etc. without opening any 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?

It gives a clear condition for the market-data use case and contrasts against the server's endpoint-scoped siblings, plus a concrete lightweight-mode instruction ('Set lite:true for market vitals + top 5 merchants'). It does not name specific alternative siblings or state when NOT to use it, so it stops short of full routing guidance.

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