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

Annotations already cover readOnly/idempotent/non-destructive, but the description adds genuinely new behavioral facts: the $0.02 cost, the scope of the verified registry (EVM and XRPL issuer lists), and that the counterparty trust tier is optional. It still doesn't say what a failing screen returns or whether results are cached/bounded, but that is beyond the annotation bar.

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 dense sentence plus a leading price token; the purpose and price are front-loaded and nothing is filler. The parenthetical registry enumeration is long but earns its place by concretizing accepted inputs.

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 read-only screening tool with full schema coverage and annotations carrying the safety profile, the description covers what is checked but says nothing about the returned verdict/flag structure or what happens when no token/address is supplied (all parameters are optional). That leaves a meaningful gap for a tool whose whole output is a pass/fail judgement.

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 100%, so all five parameters including the chain enum and address patterns are already documented; the 0-required-parameter default behavior is set by the schema. The description reinforces valid token values by listing registry tickers (btsla, rlusd, gatehub-usd, bitstamp-usd/eur), which adds modest meaning over the schema's own token examples — the 3 baseline is right.

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 specific verb+resource combination: a 'pre-trade settle-safe screen' for tokenized equities/RWAs, and enumerates the concrete checks performed (canonical registry match, freeze/clawback flags, trustline breadth, counterparty trust tier). It does not name or differentiate against siblings like wallet_screen or token_verdict, so the agent must infer that this is the composite pre-trade gate rather than a single-asset profile.

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?

'Pre-trade' and 'for AI agents trading tokenized equities/RWAs' imply the moment to use it — before settling a transfer — but there is no explicit when-not guidance and no reference to the sibling screens. Usage is inferable rather than stated.

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