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

With no annotations, the description carries the full burden. It does add useful context by stating the lookup uses 'public data', implying no auth and a read-only operation, but it never explicitly declares read-only behavior, latency, rate limits, or error conditions.

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 with zero filler. It leads with the verb and resource and then lists the checked attributes compactly.

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 simple one-parameter read lookup with no output schema, the description usefully enumerates the returned attributes (activation, balances, contract flag, blacklist bit), which compensates for the missing output schema. The main remaining gap is parameter format expectations.

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 0%, so the schema documents nothing about the single parameter. The description adds domain context by identifying the input as a TRON address, but gives no format expectations (base58 vs hex), validation rules, or error handling for a malformed address.

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?

Uses a specific verb ('Check') plus a specific resource ('a TRON address') and enumerates the checks performed (activation, balances, contract flag, USDT blacklist bit). This clearly differentiates it from quay_fee_advisor and quay_payment_verifier, though it never names those siblings 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?

No when-to-use guidance is given. The description does not state when an agent should reach for this tool versus quay_fee_advisor or quay_payment_verifier, nor any prerequisites or exclusions. Usage is only implied by the tool name.

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