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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context: the call costs nothing, and downstream payment runs over x402 with USDC on Base — information an agent needs before deciding to proceed.

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 short sentence, front-loaded with the cost signal ("Free.") that matters most for an agent deciding whether to call it. Every clause adds distinct information — inventory, price, return payload, payment rails — with no repetition of the title.

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?

With no output schema, the description carries the burden of describing returns, and it does so at field level (each tool, its USDC price, what it returns, how to pay). It stops short of describing the response shape or ordering, but for a zero-parameter catalog that is a minor omission.

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 zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly implies a parameterless call and spends no words on nonexistent inputs.

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?

"Lists every VNGRD tool with its price in USDC, what it returns, and how to pay" names a concrete verb (lists), a concrete resource (VNGRD tool catalog), and the exact fields returned. Against siblings like vngrd_voice or vngrd_transcribe, it is unmistakably the discovery/metadata tool rather than a generation tool.

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?

Leading with "Free" signals the natural usage pattern: call this first to inspect prices and payment mechanics before invoking a paid sibling. However, it never explicitly states that sequencing or names any sibling as an alternative, so the routing logic 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.