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

Goes well beyond the readOnly/idempotent annotations: it discloses the ~6 day local-node retention window, the automatic TronGrid fallback for older transactions, the `source` indicator of which backend answered, the guarantee that a local miss is not reported as 'not found', and the full metering model (5 free calls/IP/day, 0.01 USDC over x402, no API key, 402 response carries terms in structuredContent.accepts[]). This is unusually complete behavioral disclosure for a read tool.

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?

Information-dense but well front-loaded: purpose first, then when-to-use, exclusion, data source, returns, optional params, then metering. No filler sentences, though the exhaustive return-field list is long; it is defensible given there is no output 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 compensates by enumerating the returned fields and the plain-language verdict, and it covers the failure/metering mode (x402 402 response). Nothing an agent needs to call this correctly and interpret the result 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 coverage is 100%, so the baseline is 3. The description adds real meaning on top: it explains that expected_to and expected_amount_usdt cause the recipient and amount to be matched server-side rather than merely asserting what the fields are, which the schema does not convey.

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?

Opens with a specific verb+resource+scope: a TRC-20 USDT settlement check performed by transaction id. It enumerates the questions answered (did it land, irreversible, how much, from/to), which an agent can match directly against sibling tools like tron_get_transaction or tron_get_block.

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' clause (confirm a USDT payment before releasing value, closing an automated trade loop) and an explicit 'Do not use' clause routing counterparty assessment to tron_check_address_risk. Both the trigger and the exclusion are named, not implied.

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