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 'No auth required' which is critical behavioral context. However, lacks disclosure of error handling (what happens with invalid addresses), return format 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?

Two compact sentences with zero waste. Front-loaded with action verb, immediately followed by format specifics and auth status. Every word 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?

Complete for input explanation given single-parameter simplicity. However, lacking output schema, the description omits what the tool returns (converted string? object with both formats?), which would be necessary for confident invocation.

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 with format examples (T..., 41...). Description reinforces these format patterns but does not add syntax details, validation rules, or semantic constraints beyond the schema definition.

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?

Clear specific verb (convert), resource (TRON address), and scope (base58 T... vs hex 41... formats). Distinguishes from siblings like validate_address (which only checks validity) and get_account_info (which retrieves data).

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 'No auth required' which provides prerequisite guidance, but lacks explicit when-to-use distinctions from similar tools like validate_address or guidance on bidirectional conversion preferences.

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