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

Annotations only supply readOnlyHint=false, destructiveHint=false and openWorldHint=false; the description adds genuinely non-obvious behavior — access requires a valid x402 List pass token, and subordinate technology filters do not consume additional report slots. That quota/slot semantics is the kind of thing an agent cannot infer from the schema. It stops short of explaining the payment signing step or what happens when the pass is invalid or exhausted, which is why it is not a 5.

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?

Two tight sentences, front-loaded with the core action and followed by the one semantic caveat that matters. No filler, though the all-caps 'OTHRETECHS' and the phrase 'technology report slots' read as jargon that could be stated more plainly.

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 tool with 25 parameters, three required credentials, an unannotated payment flow, and no output schema, two sentences leave too much unexplained — notably which of the many filters are optional refinements versus required selections, and what the response contains. The definition covers the access gate but not the call surface.

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 description coverage is only 16% across 25 parameters, so the description must carry weight, and it only disambiguates tech ('primary technology') versus otherTechs ('subordinate filters, no extra slots'). The roughly twenty remaining filter parameters (bws, tranco, revenue, aiMaturity, spend, since, offset, etc.) get no explanation of format, semantics, or interaction anywhere in the definition.

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 gives a specific verb and resource: 'List websites using a primary technology', plus the gating condition of a valid x402 List pass. It does not distinguish itself from near-identical siblings such as list-api or mcp-list-api, so an agent cannot route between them from the text alone.

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?

Usage is implied rather than stated: the caller must already hold a valid x402 List pass, and otherTechs is flagged as subordinate. There is no explicit 'use this instead of X when Y' guidance and no mention of how it relates to x402-list-pass-purchase or the non-x402 list endpoints in the sibling set.

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