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

Beyond the readOnlyHint annotation, the description explicitly states it returns text, holds no key, and moves nothing—eliminating any risk that an agent might expect an executed on-chain transaction. This is especially valuable given the purchase-oriented name and adds meaningful behavioral context beyond 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?

Two sentences with no redundancy: the first states the core deliverable, the second enumerates outputs and safety. Every word contributes value, and the most important information is front-loaded.

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 no-input tool with no output schema, the description is complete: it specifies the deliverable (viem code), what will be reported (quote, slippage floor, fee-on-transfer method name), and the response format (text), plus the read-only safety profile. Nothing else is needed to invoke 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?

The tool has zero parameters and an empty schema, so there is no semantic burden on the description. The 'zero-shot' remark reinforces that no additional input or configuration is expected, which aligns perfectly with the schema's coverage.

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: provides ready-to-run viem code for a $BOBAI purchase with BNB on PancakeSwap V2. This clearly distinguishes it from siblings like bobai_price (price data) or bobai_guide (general guide), leaving no ambiguity about its purpose.

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?

The description implies strong usage context: an agent that needs to execute a $BOBAI purchase can use this tool and get 'everything it needs zero-shot.' It does not explicitly name sibling alternatives or state when not to use it, but the purchase-specific focus is clear enough for correct selection.

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