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

Annotations already flag openWorldHint=true, idempotentHint=false and destructiveHint=false; the description adds real substance on top: orders lock in on arrival, fill on GT's captured curve, and incur the same fees as the bot. 'Paper only' resolves the biggest behavioral question (no real funds at risk). Gaps remain around re-entering an already-entered round and what 'out' does to an open position, so 4 rather than 5.

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 core concept is front-loaded and the per-action clauses are dense but each carries information the agent needs. The closing 'Paper only. Not financial advice.' is slightly decorative, and the parenthetical parameter lists make it run-on, but nothing is materially wasteful.

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 9-parameter, nested-object, multi-action tool with no output schema, the description covers the action space, the trading mechanics and the paper-only nature, and hints at what 'state' and 'session' return. What it omits is the filter key meanings and any description of replay/session result shape, which matters given there is no output schema.

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 only 11% (just 'round'), so the description has to carry the load, and it largely does: it defines round as the coin mint, names size_sol, tp_pct, sl_pct, hold_s, delay_s, and even enumerates the filter keys (skip_red, skip_rap, min_holders, min_liq_sol, kol_in). What's missing is semantics for the 'session' integer, units/defaults for delay_s and hold_s, and the meaning of each filter, so it falls short of full compensation.

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 names a concrete subject (a paper-trading contest against SWAPNUTZ, GT's sniper, on pump.fun launches) and then enumerates all five actions with what each one does, so an agent knows exactly what the tool is. It does not explicitly contrast with any of the groundtruth_* analytics siblings, but the paper-trading framing is distinctive enough that confusion is unlikely.

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?

Each action is assigned a role and an implied sequence: 'state' lists open rounds and rules, 'in' enters one, 'session' reads a result, 'replay' backtests a strategy over 7 days of bot trades. That is clear use context. There are no explicit exclusions or 'use X instead' statements, which keeps it below 5.

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