Deep taint trace of a Tron address (paid, x402 $0.01)

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

Annotations only carry readOnlyHint=false and openWorldHint=true; the description adds substantial behavioral context beyond them: PAID via x402, moves REAL money, requires OCEANALT_PAYER_KEY, costs $0.01 USDC settled on Base mainnet, recommends a dedicated low-balance wallet, and states the analysis limits (main path only, depth ≤3, no hit does not prove cleanliness). This is far richer than the annotations alone.

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?

Front-loads purpose, then payment mechanics, then limitations, with no filler sentences. It is dense and slightly long, mixing four concerns (scope, payment, cost, caveats) into one paragraph, but every clause carries operational weight.

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?

Covers the operation, payment model, network, cost, key requirement, and limitations thoroughly — the critical facts for safe invocation. With no output schema, it does not describe the return structure (hop details, hit categories), which is the one remaining gap for a paid tracing 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?

Single required parameter with 100% schema description coverage, so the schema already documents the address format. The description confirms the Tron-only constraint and reaffirms 'USDT' semantics, adding marginal value over the schema but nothing on syntax. Baseline 3 is appropriate.

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 ('Trace a Tron (TRON) USDT address up to 3 hops back along its largest incoming transfers') and precisely what it checks for (Tether-frozen, sanctioned, mixer, scam upstream). It explicitly distinguishes itself from a single-address screen ('deeper than a single-address screen'), routing the agent away from the sibling screen_address.

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?

Gives clear context for when this is the right call versus a shallow screen ('deeper than a single-address screen') and scopes applicability ('Tron only (T…)'). It stops short of an explicit when-not or directly naming screen_address as the lighter alternative, but the comparative framing is unambiguous.

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