TRON infrastructure for AI agents.

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

With no annotations provided, the description carries full disclosure burden. It successfully adds the rental vs burn comparison behavior and the no-auth requirement. However, it omits critical safety context: it doesn't explicitly state whether this executes the call or is purely simulative, and provides no hint about return value structure or rate limiting.

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 with zero waste: purpose declaration, behavioral detail (rental/burn comparison), and usage constraint (no auth). Perfectly front-loaded with the core action in the first sentence.

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?

Appropriately complete for a 4-parameter estimation tool with full schema coverage. Addresses the core value proposition (cost estimation with comparison) and prerequisites. Minor deduction for lacking return value description given no output schema exists, though 'Estimate... cost' provides reasonable expectations.

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?

Input schema has 100% description coverage with clear type hints (e.g., 'ABI-encoded parameter hex'). The description adds no additional parameter semantics, but the baseline 3 is appropriate when the schema already fully documents all 4 parameters including optional/required status.

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 'Estimate' with clear resource targets (energy and bandwidth cost) and scope (smart contract call). The mention of 'rental vs burn cost' distinguishes this from generic estimation tools like estimate_transaction_cost or simulate, clearly positioning it within the TRON resource model context.

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?

Provides one explicit usage constraint ('No auth required'), which helps determine prerequisites. However, lacks explicit guidance on when to use this versus siblings like call_contract (execution vs estimation) or simulate, though the 'Estimate' verb partially implies read-only simulation.

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