TRON infrastructure for AI agents.

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

With zero annotations, the description carries the full disclosure burden. It successfully communicates the authentication requirement (none needed), which is critical behavioral context. However, it omits other potentially relevant behaviors such as data freshness (cached vs. live), rate limits, or the specific structure of the Merx comparison in the response.

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-sentence structure. First sentence establishes purpose with examples; second sentence states the auth policy. No redundant words or tautologies. Information is front-loaded with the core action before qualifying details.

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 zero-parameter read-only tool. Covers the essential what (network parameters), context (Merx comparison), and operational requirement (no auth). Lacks output description, but for a simple getter without an output schema defined, the description provides sufficient orientation.

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 contains zero parameters, triggering the baseline score of 4 per evaluation rules. No parameters exist requiring semantic clarification beyond the empty 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?

Excellent specificity: 'Get' is a clear verb, 'TRON network parameters' identifies the resource, and concrete examples (energy fee, bandwidth cost) clarify scope. The 'Merx price comparison' clause distinguishes it from sibling tools like get_prices or compare_providers which focus on token trading rather than network resource costs.

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 key usage constraint ('No auth required'), which helps identify when this tool is appropriate versus authenticated siblings like transfer_trx or execute_swap. However, lacks explicit guidance on when to prefer this over similar analytical tools like estimate_transaction_cost or compare_providers.

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