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 disclosure burden. It successfully communicates the authentication requirement ('No auth required') and implicitly suggests read-only behavior via 'Get' and the field list. However, it omits explicit safety confirmation (e.g., 'read-only'), error handling behavior, or rate limit warnings that would fully compensate for missing annotations.

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 efficient sentences with zero waste. First sentence front-loads the action and scope, followed by the specific metadata fields returned. Second sentence provides critical operational context (auth requirements). Every element earns its place.

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?

Appropriate for a simple single-parameter lookup tool. The description compensates for the missing output schema by listing the four return fields. Could be improved by explicitly stating the tool is read-only/safe and noting error cases (e.g., invalid token), but adequate for the complexity level.

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% with the parameter fully documented in the schema ('Token symbol or contract address'). The description adds no additional parameter guidance, but meets the baseline expectation when the schema already carries the semantic load.

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 precise verb, 'TRC-20 token metadata' identifies the exact resource type, and listing the four fields (name, symbol, decimals, total supply) clearly distinguishes this from sibling tools like get_token_price (which returns prices) and get_trc20_balance (which returns wallet balances).

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 the usage condition 'No auth required,' which helps determine when the tool is accessible (vs. authenticated alternatives). However, it lacks explicit comparison to siblings like get_token_price or get_trc20_balance to clarify when to use metadata retrieval versus price or balance queries.

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