TRON infrastructure for AI agents.

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

No annotations provided, so description carries full burden. Discloses critical behaviors: on-chain commitment ('broadcasts on-chain'), authorization requirement ('Requires TRON_PRIVATE_KEY'), and implementation detail ('automatic energy optimization'). Missing failure modes, idempotency, or return value description.

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?

Three sentences, zero waste. Front-loaded with primary action, followed by behavioral disclosure, then authorization requirement. Every sentence earns its place with no 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?

No output schema exists, and description omits return value format (transaction hash, receipt status). While authorization and on-chain effects are disclosed, a blockchain transaction tool should ideally indicate successful completion indicators or returned identifiers.

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 has 100% description coverage (all 3 parameters documented). Description adds no additional parameter semantics beyond schema (e.g., no format examples for 'human-readable' amounts or address validation rules), meeting baseline expectations for well-documented schemas.

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?

Specific verb 'Transfer' + resource 'TRC-20 tokens' clearly identifies the operation. Distinguishes from sibling 'transfer_trx' by explicitly naming the TRC-20 token standard, and from 'approve_trc20' by specifying the transfer action.

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?

States prerequisite 'Requires TRON_PRIVATE_KEY' but lacks explicit when-to-use guidance versus alternatives (e.g., distinguishing when to use this vs 'transfer_trx' for native currency or vs 'approve_trc20' for allowances). Usage constraints are implied but not explicit.

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