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 burden. It successfully notes the auth requirement but does not confirm the read-only nature of the operation, disclose rate limits, or describe what data structure is returned (e.g., single provider vs list with prices).

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 concise with two efficient sentences. The primary purpose appears first, followed by the auth note. No redundant or filler content.

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?

Appropriate for a simple 2-parameter tool, but lacks description of the return value (critical given no output schema exists) and does not mention the default behavior when optional 'amount' is omitted.

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%, so the schema adequately documents 'resource' and 'amount'. The description references both parameters ('resource and amount') but adds minimal semantic meaning beyond the schema's existing descriptions.

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 verb ('Find') and scope ('cheapest provider for a given resource and amount'). Identifies specific commodities (ENERGY, BANDWIDTH). However, does not explicitly differentiate from siblings like 'compare_providers' or 'get_prices', which also involve price analysis.

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 usage constraint ('No auth required') which is helpful context. However, lacks explicit guidance on when to use this versus alternatives like 'compare_providers' or 'list_providers', or when the optional 'amount' parameter should be included.

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