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

Annotations already establish readOnly, idempotent, non-destructive, and open-world, so safety is covered. The description adds real context beyond that: it explains the data is sourced from a radar archive limited to pools found since October 16, 2026, which tells an agent results may be incomplete for older activity. It does not describe the response shape or any latency/size characteristics.

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 identifies the subject, followed by the enumeration of returned data categories and a trailing coverage caveat. The list is dense but every item conveys a distinct data category. No filler sentences.

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, so the description bears the burden of explaining what comes back, and it does so by naming the concrete data categories (rug-pull outcomes, insider-seller roles, funding graph, creator network). What is missing is any sense of the response structure or how those categories are keyed. For a single-parameter lookup with full annotation coverage, this is close to adequate but not complete.

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?

There is one parameter and schema coverage is 100%: the schema already gives the 0x-address pattern and identifies it as a BNB Chain address. The description echoes the chain ('BNB Chain wallet') but adds no format or interpretation detail beyond the schema. Baseline 3 is appropriate when the schema carries the parameter documentation.

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 precise resource ('BNB Chain wallet') and enumerates the exact contents returned: created pools and their rug outcomes, roles held in other pools, funding relationships, and linked token creators. The verb is descriptive rather than imperative ('What the radar knows about...'), but the scope is unambiguous. Siblings (liquidity alerts, rating track record, token rating) are all token-level tools, so no confusion risk exists.

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?

Usage is implied: call this when investigating a wallet address on BNB Chain. There is no explicit statement of when to prefer this over an alternative, and no prerequisites or exclusions are given. The only guidance-adjacent content is the archive-coverage caveat, which is really a behavioral disclosure rather than a when-to-use rule.

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