tron_watch

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

With no annotations, the description carries the full burden and does so well: it discloses the incremental/cursor model (each call returns only transfers since the last call, first call covers the last hour), the lookback cap, the returned fields, the TRX balance, the per-call cost ($0.002 USDC) and p99 latency (3000ms). That is materially more than the schema provides.

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?

One dense paragraph with the purpose and polling model front-loaded, then the usage, cursor mechanics, cost and latency. Every sentence carries information; a small deduction only because cost/latency and the loop mechanics are packed into the same block without visual separation.

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?

No output schema and no annotations exist, yet the description enumerates the return fields (amount, direction, counterparty, time, link, TRX balance), the cursor chaining protocol, cost and latency, which is everything an agent needs to invoke and re-invoke it correctly.

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 the baseline is 3, but the description adds real semantics beyond the field descriptions: it explains that cursor is the value returned by the previous call, that lookback_hours applies only to the first call and is cap-limited, and that address is a Tron T-prefixed address. This is more than restating 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 specific verb and resource ('Watch a Tron address for USDT and USDC (TRC-20) transfers') and scopes the result set precisely, so it is distinguishable from siblings like tron_address, evm_balance, erc20_transfers or wallet_watch without opening any schema.

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?

Gives an explicit use context ('For deposit detection and payment confirmation on Tron'), which tells the agent when this tool is appropriate. It does not name an alternative or a when-not-to-use condition, so a 5 is not earned, but the guidance is clear and actionable.

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