TRON infrastructure for AI agents.

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

With no annotations, the description carries the full burden. It successfully communicates the auth-less nature of the call and implies speed ('Quick'), but fails to disclose error behaviors, rate limits, or what happens with invalid addresses. Missing return value description given no output schema exists.

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. Front-loads the core purpose ('Quick TRX balance') and follows with the critical behavioral note ('No auth required'). Zero redundant words.

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?

Adequate for a single-parameter tool with complete schema coverage, but falls short of full completeness due to missing description of return values (critical for a balance query) and lack of error handling context. The 'No auth required' partially compensates for missing annotations.

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% ('TRON address (T...)'), establishing a baseline of 3. The description mentions 'TRON address' but adds no semantic detail beyond the schema regarding format, validation rules, or example values.

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?

Clearly identifies the resource (TRX balance) and target (TRON address). Specifies 'TRX' which distinguishes it from sibling get_trc20_balance, though it could explicitly mention this retrieves native TRX (not tokens) to strengthen differentiation from get_trc20_balance.

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 is valuable for a blockchain tool. However, lacks explicit when-to-use guidance versus siblings like get_balance or get_account_info, and doesn't mention what format the balance is returned in.

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