TRON infrastructure for AI agents.

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

With no annotations provided, the description must carry the full burden. It successfully discloses the auth requirement (none needed), which is critical behavioral context. However, it omits other behavioral details such as rate limits, caching behavior, or what happens when an invalid address is provided.

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?

Two short sentences deliver high information density. The first sentence front-loads the return value specifics (account state components), and the second states the auth requirement. Zero redundancy.

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?

Given the simple input (1 string parameter) and lack of output schema, the description appropriately compensates by enumerating the specific data fields returned (energy, bandwidth, etc.). It meets the minimum viable standard for completeness, though error handling documentation would improve it.

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% (the address parameter is fully documented in the schema as 'TRON address (T...)'). Therefore, per the scoring rules, the baseline score is 3. The description adds no additional parameter semantics, but none are required given the complete schema.

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?

The description clearly states what the tool returns (TRX balance, energy, bandwidth, creation date) and the scope (full on-chain account state), providing specific resource detail. However, it does not explicitly differentiate from siblings like `get_balance` or `get_trx_balance` despite those being available alternatives.

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?

The phrase 'No auth required' provides a usage prerequisite, indicating when the tool can be safely called. However, it lacks explicit guidance on when to choose this over sibling tools like `get_balance` or `get_trx_balance` that return partial data.

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