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

No annotations are provided, so the description carries the full behavioral burden. It leads with 'Read-only operation — no side effects, no parameters,' clearly establishing safety. It also discloses the x402 HTTP 402 payment challenge and its exact requirements, which is important behavioral context. It does not detail response format, but it does list returned data categories.

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 three sentences, each with a distinct job: safety/no-parameters, return payload, and usage routing plus payment requirements. The critical 'read-only' attribute is front-loaded, followed by the resource being returned, and closes with actionable sibling and payment context. There is no filler or repeated schema information.

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 zero parameters, no annotations, and no output schema, the description covers the essential operational context: what is returned, when to use it, how it is paid for, and which alternatives to use. It could specify the exact response shape more precisely, but the enumerated snapshot components are sufficient for an agent to call it 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 the schema already shows an empty properties object, so the baseline is 4. The description explicitly reaffirms 'no parameters,' which reinforces the schema and prevents an agent from inventing arguments. This adds a small amount of confirmation value but is largely redundant with the structured schema.

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 the tool 'Returns the live Base market snapshot' and enumerates the contained data categories (aggregated activity, daily counters, agent catalog, real-time market data). It explicitly distinguishes itself from sibling tools by naming what get_onchain_sales and get_bot_status are for, giving agents immediate differentiation.

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 provides explicit when-to-use guidance: 'Use it for market context and price/indicator lookups.' It then names the exact alternative tools for other use cases (get_onchain_sales for paid-call revenue, get_bot_status for integration health), leaving no ambiguity about routing.

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