getDeliveryPrice

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses no authentication requirement, cursor-based pagination via nextPageCursor, and that only expired contracts are returned. No contradiction with annotations.

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 text is well-organized but redundant: 'Supports cursor-based pagination' appears twice and the 'Agent hint' paragraph largely repeats the earlier bullets and the getInstrumentsInfo exclusion.

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?

Covers use cases, supported products, authentication, pagination, output fields, and the key alternative endpoint. Missing settleCoin semantics and exact category mapping for USDC futures are the main gaps, plus no output schema means the response shape is only partially described.

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 0% schema coverage, the description compensates by explaining category as a product-type filter, baseCoin defaulting to BTC for options, symbol implied by the specific-contract use case, and cursor pagination. However, settleCoin is not addressed, and the mapping of USDC futures to the category enum is left implicit.

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 — 'Retrieve historical delivery (settlement) prices for expired futures and options contracts' — and explicitly differentiates itself from getInstrumentsInfo by excluding upcoming delivery dates. The scope is unambiguous.

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?

Provides a bulleted 'Use this endpoint when you need to' list and an explicit 'Do not use this endpoint for upcoming delivery dates — use getInstrumentsInfo' rule. The agent receives clear selection criteria.

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