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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds substantial behavioral detail: return fields, first-call lookback, cursor reuse, TRX balance, x402 pricing/payment mechanics, and a free sample. No contradiction with annotations.

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 core watch behavior, then loop/cursor mechanics, use case, pricing, and sample. Despite its length, every sentence adds operationally useful information for an agent invoking a paid, stateful tool.

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?

Given no output schema, the description compensates by listing returned fields (amount, direction, counterparty, time, link, TRX balance). It covers cursor state, first-call lookback, payment, and sample invocation, making it complete enough for correct use.

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 baseline is 3, but the description adds semantics beyond schema: first call covers the last hour, lookback_hours up to 6, and the returned cursor should be passed back on subsequent calls. Address semantics are only restated, not expanded.

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+scope: watch a Tron address for USDT/USDC TRC-20 transfers in a loop. It clearly distinguishes from generic address lookups and other chain-specific watch tools by naming Tron and the stablecoin assets.

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?

Provides clear context ('For deposit detection and payment confirmation on Tron') and explains the first-call/cursor loop. It does not explicitly say when not to use it or name alternatives such as tron_address, but the intended use case is unambiguous.

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