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

Annotations already declare readOnlyHint/destructiveHint, and the description adds substantial behavior beyond them: no API key needed, pool figures never cached vs contract properties cached up to 6h, and explicit error semantics ('tax that could not be measured comes back null with a warning, never as 0%' and 'quotable: false with a reason is an answer, not an error'). This is exactly the extra disclosure annotations cannot carry.

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 purpose and then delivers a dense, single-paragraph inventory of every returned field. The content is information-bearing rather than padding, but the run-on wall of text with no structuring is hard to parse and clearly overlong even accounting for the absence of an output schema.

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?

With no output schema, the description carries the burden of explaining returns and does so thoroughly — cost components, 1% price-impact sizes, measured tax with source, LP custody, holders, flow, venues, and contract properties. For a read-only single-parameter tool this leaves an agent well equipped to interpret results.

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?

Single parameter at 100% schema coverage, so the schema already documents that the input accepts a token address, pool/pair address, or a BscScan/DexScreener/PancakeSwap link. The description only restates 'ANY token or pool' and adds no format or resolution detail beyond the schema, fitting the baseline 3.

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 ('the full honeypot / rug-pull / liquidity read' and 'measure what a trade on BNB Smart Chain would actually cost') for ANY token or pool. It also positions itself relative to the sibling preflight ('behind the preflight'), so an agent can tell it apart from bsc_token_preflight without opening the 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?

Usage is implied by 'before placing it' and by the reference to being the deeper read 'behind the preflight', which borders on routing. However, no explicit when-to-use vs when-not, and no alternative sibling is named for cases where this is overkill — the agent must infer the relationship to bsc_token_preflight itself.

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