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

Beyond the annotations (readOnly, destructive=false), the description adds genuinely useful behavior: the call is paid, priced per call, and payable two ways (x402 USDC on Base or 1 API credit), which an agent cannot learn from the schema or annotations. It stops short of saying whether repeated calls are re-charged or cached, which matters given idempotentHint=false, and gives no latency or failure behavior.

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?

Two sentences, front-loaded with "Paid." so the cost warning lands before the agent commits, followed by report contents and then payment mechanics. No filler wording and nothing repeated from the schema.

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?

With no output schema, the description correctly spends words on what the report contains and that a short summary is included, and it discloses the payment model. Minor gaps remain around response shape details and error behavior for an invalid or non-TRON address, but the essential calling information is present.

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 schema already documents the single address parameter including a base58 T-address example. The description adds only the constraint that the report is scoped to exactly one address, with no extra format or validation detail, so 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?

"Full AML report for one TRON address" names a specific resource and scope, and the enumeration (freeze status, sanctions, abuse reports, Tether freeze history, 1-hop counterparty exposure/tracing) tells an agent exactly what the output covers. It does not name or contrast with the siblings screen_tron_address or check_tron_usdt_blacklist, so the differentiator ("full" vs a lighter screen) is only implied.

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?

Usage is only implied: the word "Full" suggests this is the comprehensive option and the sibling names suggest a lighter screen/blacklist check exists, but nothing says when to prefer this over screen_tron_address or when it is overkill. No prerequisites, exclusions, or fallback guidance are given.

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