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 identifies the external data sources (SunSwap, CoinGecko) and authentication requirements, but omits operational details like caching behavior, rate limits, error handling for unsupported tokens, or response format.

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 at 9 words. The description front-loads the action, specifies the mechanism, and states the auth requirement without redundancy. Every clause 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?

Adequate for a single-parameter tool, covering the essential function and data provenance. However, given the high sibling complexity (numerous price tools) and lack of output schema, it should provide more differentiation or behavioral context to be considered complete.

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 description coverage is 100% (token parameter fully documented), establishing a baseline of 3. The description adds no additional parameter-specific context (e.g., case sensitivity, supported token standards, or validation rules) beyond what the schema already provides.

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 clearly states the action ('Get token price') and the specific data sources ('SunSwap quote + CoinGecko USD rate'), which implicitly distinguishes its methodology from siblings like get_best_price or get_swap_quote. However, it does not explicitly clarify when to prefer this over the five other price-related sibling tools.

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?

While it notes 'No auth required' (a prerequisite), it provides no guidance on when to select this tool versus alternatives like get_best_price, get_prices, or get_swap_quote. Given the crowded namespace of price tools, this omission creates selection ambiguity.

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