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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds material context beyond them: execution on the project's own node, no key involved, and a concrete return shape including energy_used. This is genuinely additive rather than restating the annotation.

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 what the tool is before the when-to-use/do-not-use routing, and closes with a returns list. Sentences are dense but each carries new information; nothing is padding.

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 supplies the return fields (ok, contract, function, output_type, value, value_human, raw, energy_used), which is exactly the gap it needs to fill. Call contract, argument conventions, and failure modes are all covered.

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 83%, so the schema already documents contract, function, argument, argument2, parameter, and output_type. The description reinforces which TRC-20 helpers exist but adds no syntax or format detail (e.g. hex encoding of parameter) beyond the schema, 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?

States a specific verb (read), resource (any TRON contract), execution model (constant call on our own node), and scope (TRC-20 helpers built in, raw selectors for anything else). An agent can distinguish this from siblings like tron_get_contract or broadcast_raw_transaction without opening a 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?

Has explicit 'When to use' with concrete triggers (USDT balance, token decimals, allowance, any view function) and an explicit 'Do not use' clause that routes writes to a transaction tool and historical lookups elsewhere. The alternatives 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.