buy_token

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

With no annotations, the description must disclose behavioral traits fully. It mentions elastic supply (price increases) and previews before executing, but lacks details on authorization needs, rate limits, or side effects. The tax rate note helps, but more is needed.

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 very concise: two sentences plus a note. It communicates essential information without fluff, and the key point about elastic supply 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?

Given the lack of annotations and output schema, the description covers the action, price behavior, and tax implications well. It doesn't explain the return value or confirm it's a write operation, but it's fairly complete for a transaction 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?

Schema coverage is 100%, so the baseline is 3. The description adds context about USDB spending and tax rates, but doesn't provide additional parameter-level meaning beyond what's in the schema.

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 action (buy a token) and the resource (using USDB). It also notes elastic supply and price increase, which adds specificity. However, it doesn't differentiate from sibling buy tools like pm_buy or buy_order, which could cause confusion.

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 provides a note about tax rates and slippage, which gives some guidance. But it doesn't explicitly state when to use this tool vs alternatives (e.g., pm_buy for prediction markets) or when not to use it.

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