TRON infrastructure for AI agents.

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

Discloses authentication requirements (none) and implies read-only nature via 'Get'. However, with no annotations provided, the description carries full burden and omits other behavioral traits like caching, rate limits, error handling, or response format details.

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?

Two lean sentences with zero waste. First sentence front-loads purpose (what it gets, from where), second sentence adds critical behavioral constraint (no auth). Every word 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 simple 2-parameter query tool with complete schema coverage. Covers core purpose and auth, but lacks output description (no output schema exists) and sibling differentiation critical for the crowded price-tool namespace.

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 has 100% coverage with clear descriptions for both parameters ('Filter by resource type', 'Filter by duration'). Description mentions 'energy and bandwidth' which maps to enum values but doesn't add syntax details or usage examples beyond what the schema provides. Baseline 3 appropriate for high schema coverage.

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?

States specific action (Get), resource (energy and bandwidth prices), and scope (from all Merx providers). Implicitly distinguishes from siblings like get_best_price (all vs best) and get_price_history (current vs historical), though explicit guidance would strengthen this.

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?

Mentions 'No auth required' which is useful usage information, but fails to clarify when to use this versus similar tools like get_best_price, compare_providers, or get_price_history. No explicit when-not-to-use guidance.

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