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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered structurally. The description adds real context beyond that: the data is read 'straight off our own node' (freshness/provenance), and it enumerates the observable state fields including a 'found' flag implying the non-existent-address case is handled rather than erroring. It stops short of describing latency, caching, or error 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?

Content is front-loaded correctly: purpose first, then routing guidance, then return shape. It is dense but nearly every clause earns its place; the only mild excess is the closing return-field enumeration, though that compensates for the absence of an 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 assumes responsibility for the return contract and does so by listing the key fields (found, address, trx_balance, energy, bandwidth, is_witness, has_code). Combined with the explicit alternative-tool routing, an agent has everything needed to call this 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?

There is a single required parameter and schema coverage is 100%, with the schema itself documenting the base58 'T...' or 41-hex address format. The description adds no parameter-level detail beyond that, so the 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+resource (TRON account state read) and enumerates exactly what is returned (TRX balance, activation, energy/bandwidth, witness status, account age). It explicitly distinguishes itself from tron_read_contract and tron_check_address_risk, so an agent can separate it from its nearest siblings 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?

Gives explicit when-to-use conditions ('before sizing a transfer', 'checking whether an address exists on chain') and explicit when-not-to-use cases pointing to the correct alternative tools for TRC-20 balances and risk scoring. Nothing about tool 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.