bnb_fresh_launches

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

With no annotations, the description carries full burden and does well: it discloses the scanning cadence (every 2 minutes), the simulation methodology (~$1 buy then full sell next block, retried at 10%), the temporal limitation ('verdicts hold at check time only'), and the payment model ($0.01/call over x402). Rate limits and failure/retry behavior at the tool level are not covered, keeping it short of a 5.

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?

Purpose is front-loaded and virtually every clause carries information (sources, cadence, methodology, limits, pricing). It is a single dense paragraph, which slightly hurts scannability of the payment instructions buried at the end.

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 exists, and the description compensates by enumerating returned fields (round-trip loss, buy tax, sell tax, revert status) and the record shape. For a complex, paywalled honeypot tool with no annotations this is largely sufficient, though the two-call payment handshake could be spelled out more concretely.

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 schema already documents `only`, `limit`, and `payment` in detail. The prose restates the sells/traps meaning and the x402 flow but adds no syntax or constraints beyond the schema, so baseline 3 applies.

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: 'BNB Chain token launches with a honeypot check', naming the exact token sources (four.meme tokens, PancakeSwap V2 pairs vs WBNB/USDT/USDC/USD1/U). This distinguishes it cleanly from the sibling arc_fresh_launches by chain and from token_lookup/launchpad by its honeypot-simulation focus.

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 a clear two-step procedure ('Call once without `payment` for the terms, sign them with your own wallet, call again with `payment`') and ties the `only` filter to use-case (sells/traps). However, it never explicitly contrasts with siblings like arc_fresh_launches, so the agent must infer when this chain-specific tool is the right pick.

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