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

With no annotations, the description does real work: it discloses that the call is paid ($0.25 via x402 with USDC on Base or Solana) and that the response is a bulk JSON export. It omits rate limits, payload size expectations, and failure/refund behavior for the payment.

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?

A single tight sentence, front-loaded with the paywall so the agent sees cost first, then scope and contents. Every clause carries information, though it compresses a lot into one run-on.

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 one-parameter, no-annotation tool with no output schema, the description covers cost, format, temporal scope, and data contents, which is most of what an agent needs. It could still say more about expected volume and whether the export is idempotent/cached.

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% for the single date parameter, so the schema already carries the format ('YYYY-MM-DD, default yesterday'). The description only echoes 'one UTC day', adding no syntax, timezone nuance, or default behavior 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 and resource: a bulk JSON export of one UTC day of 30-minute snapshots across all 20 tracked stock perps, including cross-venue gaps, funding and OI. This clearly distinguishes it from the sample/filtered siblings, 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?

The description implies usage via 'Bulk... all 20 tracked stock perps', suggesting it is for unfiltered full-day pulls vs. the sample tools, but it never says when to prefer it over get_gaps, get_gap_sample or get_history. The paid-access note is a useful prerequisite but not usage guidance.

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