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

With no annotations, the description carries the full behavioral burden. It discloses that it is free ('Free tier. No payment required') and that it returns 'wash-filtered data using the same v2.0 algorithm as the paid endpoints,' which is valuable context about data processing. It could mention rate limits or auth, but for a read-only list tool, this is sufficient.

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, front-loaded with the core purpose, then usage guidance, then free/filter context. Every sentence adds value with no redundancy or filler.

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?

The tool is simple (no parameters) and has an output schema, so the description need not explain return values. It covers purpose, usage, and behavioral nuances like free access and wash-filtering, making it complete for this simple tool.

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 coverage is 100% trivially. Per the rubric, a 0-parameter tool gets a baseline of 4, and there is nothing to add about parameters. The description appropriately omits parameter details.

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 'List all 33 x402 service categories with aggregate stats' with specific metrics, making the tool's purpose unambiguous. It distinguishes from siblings by focusing on categories with ecosystem-level overview rather than individual services, trends, or search.

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 explicitly says 'Use this to understand the shape of the x402 ecosystem before drilling into specific services or wallets,' indicating when to use it as a starting point. It does not explicitly name alternatives, but the context implies that other tools are for deeper dives, so the guidance is clear though not exhaustive.

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