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

Beyond the read-only and idempotent annotations, the description discloses the simulation mechanics: latency slots, bonding-curve fills, curve fees, price impact, and the exact outputs including PnL, win rate, ROI per latency, and the copyability verdict. It also states the price and free quota, which is useful operational context.

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 dense but well organized: question, mechanics, fill assumptions, outputs, caveat, and pricing. A few phrases are somewhat redundant with the opening question, but each sentence carries useful information and the most important behavior 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 tool with five parameters and no output schema, the description is remarkably complete. It explains what is simulated, how fills are priced, what results are returned, how to interpret the verdict, and the cost. An agent has enough to select and invoke the tool 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?

Schema coverage is high, so the baseline is 3, but the description adds meaningful simulation context: the 1–14 day window, the latency values, the 'sells when the leader sells' behavior, and the use of most recent positions. It does not explicitly walk through each parameter, but it enriches the schema's descriptions.

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 opens with a concrete question and then states a specific verb and resource: it replays a wallet's pump.fun entries and exits with simulated latency. This clearly distinguishes it from sibling wallet-analysis tools like pump_wallet or smart_money by focusing on copy-trade profitability.

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 gives clear context for when to use the tool: when you want to know whether copying a wallet would have been profitable, including the warning that a wallet's own PnL can be misleading. It does not explicitly name alternatives or state when not to use it, so it stops short of a 5.

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