Pump Trade

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

Annotations already set readOnlyHint=false and openWorldHint=true, so the description adds minimal behavioral detail. It does not explain the bonding curve mechanics, potential slippage, or side effects beyond 'buy or sell'.

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 short but includes an unrelated SAP context sentence that could be moved to a separate field. It is not optimally concise for a tool description.

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 trading tool with an output schema, the description fails to explain return values, confirmation steps, or how the bonding curve executes. The SAP note is irrelevant to invocation completeness.

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?

Input schema has 100% description coverage, so the description adds no extra meaning. The description does not clarify the 'slippageBps' parameter's odd 'pagination control' phrasing.

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 it buys or sells tokens on Pump.fun bonding curve, distinguishing it from other trading tools. However, the SAP MCP context note is tangential and may distract from the primary 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 lacks guidance on when to use this tool versus alternatives like Jupiter or Raydium swaps. It only mentions SAP registration flow, not usage context.

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