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

Goes well beyond the readOnly/idempotent annotations by disclosing a metered payment model (5 free calls/day per IP, then 0.01 USDC over x402), the absence of an API key, and that the 402 response carries machine-readable terms in structuredContent.accepts[]. That is exactly the kind of non-obvious operational detail an agent needs before calling.

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 when-to-use, exclusions, returns, and pricing in a scannable sequence with no filler. It is on the long side because it must enumerate return fields and metering, but each sentence carries information.

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 compensates by enumerating return fields (risk_level, safety_score, hit_flags, malicious_contracts_created, account block, not_covered[], disclaimer), and it covers pricing and failure-mode handling (402 terms). Nothing needed to invoke or interpret it correctly is missing.

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 there is only one parameter, so the schema already documents the base58 'T...' address format. The description does not add syntax, validation, or format detail beyond that; 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+resource pairing: 'TRON address risk intelligence' with concrete outputs (judicial/black-market labels, account profile, 0-100 safety score). It is clearly distinguishable from sibling tron_get_account (raw account data) and tron_verify_usdt_transfer (transfer confirmation).

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?

Explicit 'When to use' with concrete scenarios (OTC settlement, merchant payout, pre-payment sanity check) and an explicit 'Do not use' that names the sibling alternative tron_verify_usdt_transfer for transfer confirmation. Nothing is left to inference.

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