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

Annotations only declare readOnlyHint and openWorldHint, and the description adds substantial context beyond them: x402 payment of 0.11 USDC on Base with the POST endpoint, sub-minute runtime, a 10% fee set aside, and an explicit statement that results are not proof of safety or financial advice. That is exactly the kind of operational detail annotations cannot carry.

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 first two sentences are dense and front-loaded with purpose, inputs and outputs, which is good. But the tail is heavy promotional boilerplate — GHOST77 token address, ERC-8004 agent ID, Virtuals ACP link, payout wallet — that does not help an agent decide or invoke; only the payment line has operational value.

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 two-parameter read-only tool with no output schema, the description covers input format, expected output ('risk level, red flags, plain verdict'), cost and latency. It does not say what happens for an unsupported network or an unrecognized contract, which is the main remaining gap.

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 100% and the network enum is enforced, so the schema already carries the parameter meaning. The description restates the two inputs and adds a concrete example payload, which is mild incremental value — the baseline 3 applies.

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 verb and resource: a fast rug/honeypot screen listing exactly what it checks (buy/sell simulation, taxes, owner powers, liquidity, LP lock, top-10 holders). The 'quick check / not an audit' framing implicitly separates it from heavier siblings like token_due_diligence or contract_security_scan, but no sibling is named outright.

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?

'For buyers checking a token before trading' gives a clear usage context, and 'Limits: automated, not an audit; a clean result is not proof of safety' sets an explicit boundary on how much to trust it. No alternative tool is named for deeper analysis, so the agent must infer that from sibling names.

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