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

With no annotations, the description carries the full burden and does declare 'read-only,' which is the key safety fact, plus a concrete enumeration of the five checks it runs. It stops short of saying what the result looks like or whether any finding should block the send, which matters for an advisory tool with no output schema.

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 the read-only property first and the check list after a colon. Every element earns its place and nothing is padded.

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 four-parameter, fully documented, read-only advisory tool, the description covers purpose, safety profile and the dimensions being tested. Its only real gap is the absence of any hint at the return shape (flags vs. verdict), which is notable since no output schema exists.

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 description coverage is 100%, so 'to', 'from', 'token' and 'amount' are already documented. The description reinforces the token dimension ('TRX or USDT', 'token contract') but says nothing about 'amount' or why dust checking might depend on it, so it adds only marginal meaning over 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?

The description names a specific verb (preflight) and resource (a TRX/USDT send) and enumerates the exact checks performed: look-alike destination, dust, new/inactive recipient, USDT blacklist, token contract. It is clearly distinguishable in spirit from quay_fee_advisor or quay_address_check, though it never names a 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?

The trigger is stated plainly: run this before a TRX or USDT send. That gives an agent a clear point of use, but the description offers no exclusions and does not say how this differs from the narrower quay_address_check or when to skip it (for example, non-TRON assets).

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