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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds substantial behavioral detail: it returns stop[] and caution[] facts, does not say 'safe' or return a score, cannot see unacted owners, and is built from other tools. It also discloses no API key and no caching, going well beyond the 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?

The description is long but every sentence carries meaning: it front-loads the purpose, then details return structure, special cases, and limitations in a logical flow. It is well-structured with clear sections (stop[], caution[], figures) and no filler.

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?

For a complex pre-trade analysis tool with no output schema, the description covers return types, data sources, special cases (four.meme), limitations (cannot see unacted owner), and operational details (no API key, no caching). Nothing critical an agent needs to call it correctly is missing.

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%, with both parameters described (address and usd). The description adds context that usd is the trade size and that the tool works 'at YOUR size', but does not add syntax or format details beyond the schema. With full schema coverage, the baseline of 3 is appropriate.

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 clearly states the tool's purpose: a preflight check for trading any BSC token, answering whether you can get in, get out, and at what cost. It distinguishes itself from its component tools (bsc_pool_scan and pancakeswap_best_route) by positioning as the aggregated pre-trade check, making its unique value obvious.

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?

It explicitly says 'the check to run before every trade' and notes it is built from bsc_pool_scan and pancakeswap_best_route, implying it is the primary pre-trade tool. It does not explicitly state when to use alternatives, but the context and mention of component tools provide clear usage guidance.

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