okx_get_quotes

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

No annotations provided. The [L:READ] tag hints at a read operation, but the description does not disclose any behavioral traits such as side effects, authorization requirements, or limits. With no annotations, more detail is needed.

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?

Description is very short, which is concise, but the use of tags and Chinese characters may reduce clarity for English-speaking agents. It is structured with tags but sacrifices comprehensibility.

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 the tool's complexity and many siblings, the description fails to provide enough context. It does not explain what data is returned, how the tool fits into the RFQ workflow, or what 'quotes' means. No output schema exists to compensate.

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 parameter 'rfqId', whose description already states 'RFQ ID。必填'. The tool description adds no additional semantic value 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?

Description is vague; uses tags [L:READ] and category but does not explicitly state what the tool does. The user must infer from sibling tools and parameter name 'rfqId' that it retrieves quotes for an RFQ. Lacks a clear verb+resource statement.

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 prerequisite ('请先调用 agent_catalog') but no guidance on when to use this tool vs alternatives like okx_get_rfqs or okx_execute_quote. No comparison or context for selection.

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