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

Annotations already cover read-only and open-world nature; the description adds genuinely non-obvious behavior: a $0.25 USDC charge per call settled via x402 inside the call, and that failed calls are not charged. It also discloses data provenance (Bazaar discovery + Base settlements) and that figures are adjusted for sweeps. Missing only things like latency or freshness lag relative to 'latest' week.

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?

Opens with a framing question, then front-loads the payload description, then usage, then pricing — a sensible order with no filler. The middle sentence is dense with a long comma list but every item describes report contents an agent would want. Slightly heavier than needed but not wasteful.

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 single-optional-parameter read tool with no output schema, the description tells the agent what sections come back, where the data originates, and what it costs — enough to decide and call. It stops short of describing response shape or pagination/size, which matters somewhat for a report-style tool with no output schema.

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?

Only one optional parameter and the schema documents it at 100% coverage ('ISO week; latest if omitted'), so the schema already carries the semantics including the pattern and default. The description adds nothing about the week argument. Baseline 3 is correct when the schema does all the work.

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 resource (weekly x402 market/demand report) and enumerates its contents: repeat-use demand by category, demand gaps, movers, price bands, GET vs POST traction, with sources and sweep adjustment. That is far more specific than the title alone. It does not explicitly contrast itself with siblings such as demand_gaps or payer_analytics, though the enumeration implies this is the superset report.

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?

States a clear usage condition: 'Use when an agent needs x402 demand by category before choosing what to build or how to price it.' That gives the agent a decision context. No exclusions or named alternatives (e.g., when to prefer demand_gaps for a narrower answer) are given, so it stops short of a 5.

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