getNewDeliveryPrice

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

Discloses data delay up to 1 minute, default limit of 50 records, no authentication required, reverse chronological order, and default settleCoin=USDT. No annotations provided, so description carries full burden and meets it well.

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?

Well-structured with bullet points and sections. Front-loaded with main purpose. Slightly redundant (agent hint repeats info) but overall efficient.

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?

Comprehensive given 3 parameters, no output schema, and many siblings. Covers use cases, constraints, timing, defaults, and alternatives. Includes agent hints.

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 has 0% coverage, but description adds meaning: category must be 'option', baseCoin required, settleCoin defaults to USDT. This compensates for missing schema descriptions.

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?

The description clearly states it retrieves historical option delivery prices grouped by base coin and settlement coin in reverse chronological order. It explicitly distinguishes from sibling getDeliveryPrice by specifying it's for options and not futures.

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 explicit when-to-use (look up recent option settlement prices by base coin, retrieve latest delivery price after settlement) and when-not-to-use (futures delivery prices -> use getDeliveryPrice, specific contract symbol -> use getDeliveryPrice). Also advises waiting 1 minute after settlement.

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