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

Goes well beyond the readOnlyHint/openWorldHint annotations: it explains the simulation method (real holders attempt transfers, Uniswap quoting), enumerates verdict outcomes (sellable, costly, blocked, partial), and discloses billing behavior (only an answer is billed; unknown or untestable exits are free). It also frames the result as a simulation, not a signal. This is rich, non-obvious behavioral 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?

Front-loads the usage trigger, then method, then output and billing caveats, so an agent reads the most important line first. Dense but nearly every sentence adds information; the closing 'never a buy or sell signal' disclaimer is useful but slightly padded.

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?

With no output schema, the description carries the return-shape burden and does so well: it lists the verdict, round-trip return and cost, transfer test, and LP-burn share. Combined with billing behavior and caveats, an agent has everything needed to call it 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 100%, so both the address and quote parameters are already documented in the schema, and the description adds no format or syntax detail beyond it. The billing sentence loosely relates to the quote flag but comes from the behavioral angle rather than parameter semantics. Baseline 3 is appropriate.

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?

States a precise verb and resource: simulates a token exit on Robinhood Chain to determine whether the token can be sold back and at what cost. The scope (on-chain exit simulation, buy-then-sell round trip on Uniswap) clearly distinguishes it from siblings like scan_token or new_launches without needing to name them.

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?

Gives explicit timing context: 'Use this right before buying a Robinhood Chain token,' which frames a clear trigger. It does not name alternative tools or state when not to use it, but the intended usage moment is unambiguous.

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