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

With zero annotations the description carries the full burden and does so: it discloses the price ($0.05 USDC), the accepted chains (Base or Solana), that no account or API key is needed, that failed calls are not charged, and the endpoint URL. That is exactly the payment/auth/risk context an agent needs before invoking a paid call.

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?

Five short sentences, front-loaded with the "Paid" signal and the data description before the payment mechanics and URL. No filler and nothing repeated from the schema.

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, single-feed purchase tool with no output schema or annotations, the definition covers what it returns, what it costs, how payment works, and where it points. Nothing an agent needs in order to call it correctly is missing.

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 schema has zero parameters, so there is nothing to disambiguate and the baseline is 4. The description does not add parameter meaning, but none is needed.

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?

"CHAINNOVA NETWORK (CHNET) price: live USD price, 24h change and market-cap rank" names the exact resource and the three fields returned. Because the siblings are hundreds of identically named per-token buyers, the token symbol in the name plus the spelled-out token name is what makes this distinguishable, and the description supplies both.

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 context is implied by the price-data framing and the "Paid" marker, so an agent knows it is buying a CHNET quote. However, it never says when to prefer this over a generic sibling or what to do on failure, and there are no explicit exclusions.

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