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

readOnlyHint=true already tells the agent this is a safe read. The description adds useful substance by disclosing that entries carry price, inputs, and an equivalent x402 HTTP URL — behavior beyond the bare annotation. It says nothing about pagination, size of the catalog, or formatting of the returned entries, so it stays at an adequate rather than rich level.

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?

One sentence, zero filler, with the what and the returned fields front-loaded. Nothing could be cut without losing 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?

For a zero-argument catalog tool with no output schema, the description tells the agent what each entry contains, which is the key missing structured detail. Only mild gaps remain (ordering, catalog breadth), so it is complete enough to call 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 takes no parameters at all, so there is nothing for the description to disambiguate. The baseline of 4 applies, and the description does not confuse matters by mentioning inputs the tool does not accept.

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?

States a specific verb and resource ('Lists every BaseLens tool') plus the fields returned (price, inputs, x402 HTTP URL). This clearly separates it from the sibling lookup tools, which each target a single chain resource.

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 catalog/discovery use case is strongly implied by 'lists every BaseLens tool with price', but there is no explicit when-to-use statement, no mention of when not to use it, and no named alternative (e.g., base_price for a single price). Guidance is inferred rather than stated.

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