bobai_how_to_buy

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

No annotations are provided, so the description bears full responsibility. It discloses the method (viem code, PancakeSwap V2, slippage, fee-on-transfer) but does not mention prerequisites (e.g., needing BNB, wallet setup), execution environment, or return value format.

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 a single, well-structured sentence that is front-loaded with key information. Every word is informative and concise.

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?

Given no parameters and no output schema, the description provides a clear purpose and output (code for swap). It is slightly vague on the exact form of the return (code snippet? instructions?), but overall complete for a no-param tool.

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 are no parameters (0 params, 100% schema coverage). The description adds full context about what the tool does without needing parameters, earning a baseline of 4.

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 provides 'Ready-to-run viem code to BUY $BOBAI with BNB on PancakeSwap V2', specifying action, asset, pair, platform, and method. It distinguishes from siblings (e.g., bobai_price, bobai_activity) which are informational.

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 says 'so an agent can execute a swap 0-shot', indicating intended use for direct buying. It does not explicitly state when not to use or name alternatives, but the context of sibling tools implies this is the execution tool, while others are for queries.

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