Robinhood Chain per-trade reserves ($0.02)

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

Discloses behavior the annotations do not: per-page pricing ($0.02), cursor-based pagination via next_cursor, freshness bound (90 min), returned state check against prior state, and the free sample route. Annotations only carry generic hints (readOnlyHint=false, openWorldHint=true), so this extra cost/pagination/freshness context is genuinely additive.

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 price and usage, which is good, but the field enumeration after 'in block order:' is a dense colon-chained run-on that is hard to scan. The information is mostly warranted (no output schema exists), yet the structure could be split into discrete sentences.

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 usefully enumerates the returned fields (amounts, fee, snipe/creator tax, Q and T, price Q/T, multiple vs launch, graduation share, next_cursor), and it covers cost, pagination and freshness for a 3-param tool. Only a clearer statement of failure/coverage limits is missing.

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?

With 100% schema description coverage the schema already documents address, since (cursor/block/unix seconds) and limit. The description's 'Input:' sentence largely restates those fields, adding only the framing that address may be a curve or token, which the schema also states. Baseline 3 applies.

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 and resource: reserves after each trade on a Robinhood Chain pons curve, rebuilt per buy, sell and fee-sweep buyback in block order. An agent can distinguish it from aggregate siblings like rhc_curve_card, though no sibling is named explicitly.

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 clear trigger conditions ('Use when you index or price a pons curve and need the reserves after each trade') plus a scope restriction ('ETH-paired curves up to 90 min old') and a free sample endpoint to check coverage first. No explicit when-not or named alternative, so not a 5.

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