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

With no annotations, the description carries the full burden and does well: it discloses that the call is paid ($0.01 USDC on Base or Solana), that no credentials are needed, and that failed calls are not charged — billing behavior that materially affects invocation decisions. It omits latency/data freshness and response format, keeping it short of a 5.

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?

Four short clauses, front-loaded with the payment flag and the data payload, followed by cost, prerequisites, billing terms, and endpoint. No filler and nothing repeated from structured fields.

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, output-schema-less price fetch, the description tells the agent what data comes back, what it costs, how to pay, and that failures are free — enough to call it confidently. Only freshness/latency and response encoding are left unstated.

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 the baseline of 4 applies; there is nothing for the description to disambiguate. The endpoint URL is included, which is the only useful invocation detail beyond the schema.

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 resource (Opcode/OPCODE token price) with the exact payload it returns — live USD price, 24h change, market-cap rank. The name and description are unambiguous enough to separate it from the hundreds of sibling buy_tok_* and buy_coin_* tools that cover other symbols.

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?

Implied usage is clear (call it to get OPCODE's price), and prerequisites are covered ('No account, no API key'), but there is no explicit routing advice against alternatives such as buy_crypto_price or buy_coin_* variants of the same asset. The agent must infer when this paid per-token endpoint beats the generic price tool.

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