execute_buy

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

With no annotations, the description bears the full burden. It usefully discloses the multi-stage pipeline (risk-check -> build -> sign -> broadcast) and the required env flag/keypair, which signals an irreversible on-chain write. It stops short of saying the transaction is irreversible, that funds leave the wallet, or how a failed risk-check is surfaced.

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, zero filler, with the action sequence front-loaded and the prerequisite relegated to a second sentence. Every clause carries information.

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 real-money mutation tool with no annotations and no output schema, the description covers the operation and auth gate but omits slippage semantics, the failure mode when the risk check fails, and whether a transaction signature is returned. Adequate but with recognizable gaps.

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 67%: mint and usdAmount are described in the schema (usdAmount even carries the $10-$20 bound), but slippagePct is undocumented in both places. The description adds no parameter-level meaning of its own, so this sits at the baseline-3 level for partial 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?

The description gives a precise verb chain ("Risk-check, build, sign, and broadcast") applied to a specific resource ("a pump.fun buy"). An agent can immediately tell this executes a real trade, and "broadcast" implicitly separates it from the prepare_buy sibling, though that sibling is never named.

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 states a prerequisite (AUTO_TRADING_ENABLED=true, configured keypair) but never says when to reach for this tool versus prepare_buy or the sell path. No conditions, no exclusions, no alternative routing are given, so the agent must infer usage from the name alone.

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