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 source (CoinGecko) and authentication requirements (none), but omits operational details like rate limiting, caching behavior, error modes, or whether the operation is idempotent/read-only.

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. Information is front-loaded with the core action, followed by critical operational metadata (auth). Zero extraneous text.

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?

For a simple single-parameter read operation without an output schema, the description adequately covers the essential context: what it returns (TRX price), from where (CoinGecko), and access requirements. Slight gap in not describing the return value format or numeric precision.

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% (the 'currency' parameter is fully documented in the schema with default value noted). The description adds no additional parameter semantics, meeting the baseline score for high-coverage schemas.

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?

Description provides specific verb ('Get'), resource ('current TRX price'), and data source ('from CoinGecko'). The specificity of 'TRX' distinguishes it from generic sibling 'get_token_price', while 'current' distinguishes it from 'get_price_history'.

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?

The description notes 'No auth required', which provides one usage constraint, but fails to explicitly state when to use this tool versus siblings like 'get_token_price' (which could also fetch TRX) or 'get_prices'. No prerequisites or exclusions are mentioned.

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