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

With no annotations, the description carries the behavioral burden. It discloses that the call is paid ($0.01 via x402), that it combines two third-party data sources, and that the output is a categorical recommendation. It doesn't mention failure modes or exact return formatting, but the core semantics are clear.

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 and packs in purpose, data sources, output, cost, and alternative behavior. It is slightly promotional and starts with price, but it remains tight and front-loads the high-level function.

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 simple paid aggregator with one required parameter, the description covers what the tool does, what it costs, what it returns, and how it differs from chaining alternatives. Without an output schema, it names the recommendation categories, which is sufficient guidance for invocation.

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 already describes address and chain, with 67% coverage. The description adds the aggregator context and the payment mechanism, but the x_payment parameter remains unexplained in both schema and description. Baseline 3 is fair because the description partially compensates but doesn't fully cover the unknown parameter.

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 names a concrete resource ('token intelligence'), a specific action/outcome ('fuses GoPlus rug-check + Dexscreener market data into a single GO/CAUTION/AVOID recommendation'), and an aggregation role. This clearly separates it from sibling tools like token_security_check and dex_token_data.

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?

It states the intended use case: the aggregator call trading and sniping agents make 'instead of chaining rug-check + dex separately.' This gives an explicit alternative, though it does not spell out when an agent should instead call token_security_check or dex_token_data alone.

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