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 the full burden. It discloses 'No authentication required' (a key behavioral trait), but omits other critical behavioral context like whether the calculation is deterministic, rate limits, or what the return value contains.

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?

Extremely efficient: two declarative statements with zero redundancy. The purpose is front-loaded and the auth note provides essential context without verbosity.

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 100% schema coverage for 2 simple parameters, the input side is well-covered. However, lacking an output schema and annotations, the description should ideally disclose what the calculation returns (amount, percentage, breakdown) and whether the operation has any side effects.

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 100%, establishing a baseline of 3. The description adds no explicit parameter semantics, though the schema already fully documents the 'operation' enum values and 'transaction_count' defaults.

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 uses a specific verb ('Calculate') and clearly defines the resource ('savings from renting energy vs burning TRX'), distinguishing it from siblings like 'estimate_transaction_cost' (which estimates cost) and 'compare_providers' (which compares providers).

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 description implies the use case (comparing energy rental vs TRX burning costs) but provides no explicit guidance on when to choose this over 'estimate_transaction_cost' or prerequisites for the calculation.

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