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

With no annotations, the description carries the full burden. It usefully discloses the cost ($0.01 USDC) and the epistemic caveat ('Heuristic screen, not financial advice'), which are real behavioral traits. However, it omits permission/auth needs, rate limits, and how the payment parameter is consumed, leaving meaningful gaps.

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 imperative 'START HERE' is front-loaded, and every sentence adds a distinct fact: decision output, cost, alternative tool, and disclaimer. No redundancy or filler.

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?

An output schema exists, so the description needn't detail return values, though it helpfully summarizes them. It covers cost and the heuristic caveat, but the absence of any parameter explanation leaves the definition slightly incomplete for a 4-parameter tool.

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% and four parameters (chain, address, payment, amount_usd) are undocumented in structured data. The description only alludes to the price ('$0.01 USDC'), which loosely maps to amount_usd, but never explains chain, address, or the payment parameter. It does not compensate for the coverage gap.

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 specific action and output: 'One call returns a buy / watch / avoid decision with the reasons, risk score, key numbers...'. It also distinguishes itself from the sibling precheck by routing raw-data seekers there, so an agent can tell them apart without opening either schema.

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?

'START HERE before buying a token' gives a clear trigger condition, and 'For full raw data use precheck' names the explicit alternative. It stops short of an explicit when-not-to-use (e.g., for already-held positions or non-token assets), but the usage context and routing are clear.

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