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

Annotations already cover read-only and non-destructive behavior, and the description adds meaningful context the annotations cannot: prepaid credit pricing at 0.0005 USDT per 100 rows, the need to call orbitpay_info first, and an alternative 0.01 USDC x402 path. It does not explain pagination behavior with the cursor or the shape of the returned series.

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 compact sentences that front-load the resource and then the payment mechanics, with the HTTP fallback at the end. No filler, though the URL detail is dense and somewhat tangential to invocation semantics.

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, a nested filters object, and zero schema description coverage, the description should explain what the series contains and how filtering/pagination work. It covers monetization well but leaves the actual call semantics underspecified.

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 0% across five parameters including a nested free-form filters object, and the description supplies no parameter meaning at all. Only 'over time' hints that from/to are a time range; limit, cursor, and the filters keys are left entirely undocumented.

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 the resource and its content clearly: 'Premium Wanchain economics time series (supply, fees, and related metrics over time).' That distinguishes it from siblings like get_network_stats or get_wan_deflation, though the verb is implicit rather than stated as an action.

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?

Gives concrete routing for the payment path (call orbitpay_info, or use x402 on the HTTP route), which is genuinely useful. However it never says when to prefer this premium series over free sibling tools such as get_wan_deflation or get_network_stats, leaving the main selection decision to inference.

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