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

With no annotations, the description must carry the behavioral burden. It usefully discloses that this is a read-only public-chain lookup and that it is free, plus exactly which facts come back, but it omits what happens for malformed or non-activated addresses and whether any auth or rate limits apply.

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?

A single front-loaded sentence names the purpose, the use moment, and the return fields with no filler. Slightly dense colon-list format, but every clause 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?

There is no output schema, but the description compensates by listing the five returned facts, which is enough for a one-parameter lookup tool. The remaining gap is error/edge-case behavior for invalid addresses, which matters for a tool whose main risk is a typo'd address.

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 single parameter is fully documented in the schema as a base58 TRON address starting with T, so the baseline is 3. The description adds only contextual framing (an address you intend to send USDT to) and no format, validation, or edge-case detail beyond the schema.

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 concrete verb and resource ('Public chain facts about a TRON address') and enumerates the returned facts (activation status, age, TRX balance, USDT balance, tx count). It is clearly distinct from cost-oriented siblings like trc20_transfer_cost, though it never names or contrasts any sibling explicitly.

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?

'before you send USDT to it' gives a clear triggering scenario, which is more than most tools provide. It stops short of stating exclusions or naming alternatives (e.g., trc20_transfer_cost for fee estimation), so the agent must infer when another sibling is the better fit.

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