getNewDeliveryPrice

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

Annotations only declare readOnlyHint and openWorldHint; the description adds valuable behavior: reverse-chronological ordering, up to 1-minute data delay, default limit of 50, and no authentication required. This goes well beyond the structured annotations and contains no contradiction.

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-organized with bolded sections and bullets, and the key constraints are front-loaded. However, the 'Agent hint' mostly restates the same required-parameter and getDeliveryPrice guidance already given, adding avoidable duplication.

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 simple read-only 3-parameter query with no output schema, the description covers what is fetched, when to call it, which sibling to avoid, timing delay, default limit, and auth requirements. Nothing essential for an agent to invoke it correctly 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?

Schema has 0% description coverage, so the description carries the full parameter burden. It states that category=option and baseCoin are required, gives concrete examples for baseCoin (BTC, ETH), and documents settleCoin's default of USDT. This is sufficient for correct invocation.

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?

Description opens with a specific verb and resource: 'Retrieve historical option delivery prices grouped by base coin and settlement coin' and specifies ordering. It explicitly limits to options and names getDeliveryPrice as the sibling for futures, so an agent can distinguish this tool from its near neighbor.

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 'Use this endpoint when you need to' bullets and two 'Do not use' rules naming getDeliveryPrice as the alternative. It also adds a timing condition (wait at least 1 minute after settlement) that governs when the call is appropriate.

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