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

Annotations already declare a safe, idempotent read, but the description adds the critical trait they cannot express: the node is a lite full node with a ~6 day window, so an empty result means 'outside our window', not 'payment missing'. That single constraint prevents a serious false-negative interpretation and is exactly the beyond-schema value this dimension rewards.

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 the capability, then uses labeled clauses ('When to use', 'Do not use', 'Boundary', 'Returns') so an agent can scan to the part it needs. Despite being dense, no sentence is redundant and each carries distinct decision-relevant content.

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?

There is no output schema, and the description compensates by enumerating the returned fields (found, block_number, status, contract_type, owner/to/contract_address, amount_trx, trc20_transfers[], energy_used, confirmations, finalized, retention_window). Combined with the retention-window caveat, an agent has everything needed to call it and interpret results correctly.

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% for the single txid parameter ('64 hex char Tron transaction id'), so the schema already documents it. The description adds only 'by txid', and its field list ('found, block_number, status...') describes the return rather than the parameter, so baseline 3 is correct.

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 ('One Tron transaction by txid') and immediately enumerates what the caller learns: success/reverted, energy used, the call made, and decoded TRC-20 transfers. It names the siblings it is not for (tron_check_address_risk, tron_get_block), so an agent can distinguish it without opening any schema.

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' framed around a concrete task (did this USDT payment land, for how much, from whom, is it finalized), explicit 'Do not use' with the two sibling alternatives named, and an additional fall-back rule for empty results. Nothing about selection 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.