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 full behavioral disclosure burden. It adds valuable operational context ('No auth required') and output characteristics ('trends and recommendations'), but omits whether the operation is read-only, rate limits, or how recommendations are generated.

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?

The description consists of two efficient sentences with the primary purpose front-loaded. Every word earns its place, though the extreme brevity leaves gaps in sibling differentiation and parameter context that a slightly longer description could address.

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 single-parameter tool without output schema, the description adequately hints at return values ('trends and recommendations'). However, given the presence of numerous sibling price tools and lack of annotations, the description should specify the analysis scope (ENERGY/BANDWIDTH) and ideal use cases to be truly 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 coverage is 100% (the resource parameter is fully documented as 'Filter by resource type. Omit for all.'), establishing a baseline of 3. The description adds no explicit mention of the resource parameter or its ENERGY/BANDWIDTH enum values, but the schema sufficiency prevents a lower score.

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 states it performs 'Market price analysis with trends and recommendations' which uses a specific verb and suggests output format. However, it fails to mention the critical constraint that this only analyzes ENERGY and BANDWIDTH resources (as revealed in the schema), leaving the scope ambiguous regarding whether it supports tokens, commodities, or other assets.

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 note 'No auth required' provides one usage constraint, but there is no guidance on when to use this tool versus siblings like get_price_history, get_best_price, or get_prices. Given the crowded namespace of price-related tools, explicit differentiation is needed but absent.

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