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

With no annotations, the description carries the full burden, and it does disclose two valuable traits: the reference price may come from Chainlink or a market quote, and the call costs $0.002 USDG. It does not explain failure modes (symbol not found, no pool), data freshness/latency, or whether the reference source can be controlled — meaningful gaps for a paid live-data read.

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?

Two tight sentences, zero waste, and the core purpose is front-loaded before the return contents and the price. Nothing needs trimming.

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?

There is no output schema and no annotations, so the description must sketch the return, which it does: gap, pool depth, timestamps. The price disclosure is a useful extra. It falls short only on error/freshness behavior and on the relationship to the gap_board sibling.

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 description coverage is 100% and the single parameter is documented with an example ('Stock ticker, e.g. NVDA'), so the schema does the heavy lifting. The description adds only that the token is a stock token, no extra syntax or validation detail beyond the schema.

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 specific verb+resource: it returns the live on-chain price gap between pool price and reference price for a single stock token, plus pool depth and timestamps. The phrase 'for one stock token' implicitly separates it from parallax_gap_board, but the sibling is never named, so the agent must infer the distinction.

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?

Usage is only implied — an agent can infer it should call this when it needs a gap for one specific ticker. There is no explicit when-to-use, no guidance on picking this over parallax_gap_board or parallax_pricing, and no stated behavior for unknown or unlisted symbols.

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