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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower. The description adds meaningful context beyond them by stating the data comes 'straight off our node' rather than an aggregator, and by enumerating the returned fields despite there being no output schema; it does not mention caching, staleness windows, or rate limits.

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?

Front-loaded with the resource identity, then usage routing, then returns — a sensible order. The opening sentence's field list is partially redundant with the later 'Returns' enumeration, which costs it a point, but every section still carries selection-relevant information.

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?

With no parameters and no output schema, the description is the only place an agent can learn the return shape, and it supplies that as a concrete field list (energy_fee_sun_per_unit, transaction_fee_sun, next_maintenance_ms, etc.). Combined with the sibling disambiguation, nothing needed for correct invocation is missing.

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?

The tool takes zero parameters, so there is nothing to disambiguate and the baseline is 4. The description appropriately spends its words on outputs rather than inventing parameter guidance.

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 a precise verb+resource ('TRON chain economics') and enumerates the exact quantities returned (energy price, transaction fee, account creation fee, witness pay, maintenance interval, unfreeze delay). It also explicitly disambiguates from the sibling fee tools btc_get_fee_rates and xmr_get_fee_rates, so an agent can select it without opening the schema.

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?

Contains an explicit 'When to use' clause (working out transaction cost in TRX, checking resource-market pricing) and a 'Do not use' clause that names the two alternative tools for Bitcoin and Monero fees. Both the positive and negative selection conditions are spelled out.

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