getDeliveryRecord

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

Lacking annotations, the description explains time range behavior and account coverage, which are useful. However, it does not disclose read-only nature, authentication needs, or any side effects. For a query tool, this is acceptable but could be more transparent.

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 description is concise, using bullet points for time range rules for clarity. It is well-structured and front-loaded with the core purpose. Every sentence adds value, though it could be slightly more 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?

Given 7 parameters and no output schema or annotations, the description lacks completeness. It misses parameter explanations, return value description, and usage prerequisites. The time range rules are well-covered, but overall, the agent needs more context to use the tool correctly.

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 description coverage, the description only indirectly explains startTime and endTime via time range rules. It omits explanations for category, symbol, expDate, limit, and cursor, which are in the schema. The description adds minimal semantic value for most parameters.

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 queries delivery records of USDC futures, Inverse futures, and Options, and differentiates account types (Unified vs Classic). The verb 'Query' and resource 'delivery records' are specific and distinct from siblings like getTradeHistory or getOrderList.

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 provides detailed time range rules which guide when parameters are needed, but it does not explicitly state when to use this tool over alternatives or provide exclusions. No comparison with sibling tools is given.

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