List paid tools and prices

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

No annotations are provided, so the description carries the burden. It discloses that the tool is 'FREE' (no cost), that it lists 'every' paid tool (comprehensive scope), and that pricing is in USDC.e. This goes beyond the schema and provides useful behavioral context, though it does not explicitly state read-only nature or response format.

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 two sentences, front-loaded with the key differentiator 'FREE,' immediately followed by the action and scope. Every word earns its place with no redundancy.

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-parameter, no-output-schema tool, this description is sufficiently complete. It explains what the tool does, the cost implication, and the recommended usage order. It could add a note about read-only semantics, but given the simplicity, it covers essential context well.

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, so there is nothing to document. The description correctly omits parameter details. The baseline for 0-parameter tools is 4, and the description adds no unnecessary param information.

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 a specific verb ('Lists') and resource ('every paid tool in this server') with a clear scope ('with its price in USDC.e'). It clearly distinguishes itself from sibling tools by being the only tool that lists paid tools and prices, rather than providing market data or wallet info.

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?

Explicitly instructs to 'Call this FIRST to see what is available and what it costs,' giving clear contextual usage. It does not mention alternatives or exclusions, but as a unique listing tool, there are no direct alternatives to compare against.

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