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

Annotations already cover read-only, idempotent, non-destructive, and closed-world behavior. The description adds important context beyond annotations: it is a no-real-trade replay, uses conservative reserve fills and costs, has per-tier rate/quota limits, and has partial historical coverage starting October 3, 2026.

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 front-loaded with the core action and then efficiently layers quota, simulation, historical-coverage, and date-range guidance. Every sentence carries useful information for an agent deciding whether and how to call the tool.

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?

The description covers important operational context such as quotas, date limits, history start, dataset variability, and the absence of real trades. For a complex nested-rule tool with no output schema, however, it does not explain what a replay result contains or define the rule fields, leaving notable gaps for correct invocation.

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 moderate at 60%, and the description helps with date-range semantics by pointing to days_available and noting the 10-day cap for covered days. However, it does not explain the core rule object fields such as entry filters, exit conditions, or position_sol, leaving the most important nested parameter semantics to the schema alone.

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 states a specific verb and resource: replay a structured rule on recorded PumpSwap trades. It also clarifies that this is a simulation with conservative reserve fills and costs and that no real trades occur, which distinguishes it from data-retrieval siblings.

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 gives concrete usage constraints by access tier, including free daily limits and paid covered-day/key quota limits, plus a maximum of 10 days per call. It also directs the agent to days_available for the exported UTC day range, though it does not explicitly say when to choose this tool over all other siblings.

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