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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'this tool holds no key and moves nothing' plus 'Returns text'. It also discloses the quote/slippage behavior. It stops short of noting rate limits or latency, but for a read-only code generator this is solid added context.

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 the purpose, then outputs, then routing, with no wasted preamble. The middle sentence is dense but each clause carries meaning; slightly run-on.

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 zero-parameter, read-only tool with no output schema, the description states the return type ('Returns text') and the content of the generated code (quote, slippage, fee-on-transfer method name). An agent has everything needed to call 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?

Zero parameters, so there is no schema surface to interpret and the baseline is 4. The description correctly implies a parameterless, self-contained call.

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: it produces ready-to-run viem code for a $BOBAI purchase with BNB on PancakeSwap V2. It explicitly contrasts with the sibling bobai_dex_info ('for the raw parameters only'), so an agent can route without opening either 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?

Explicit when-to-use ('Use it when you want working code') plus a named alternative and its selection condition ('for the raw parameters only, bobai_dex_info'). Nothing is left to inference.

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