okx_get_rfq_trades

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

No annotations provided. The tag '[L:READ]' hints at read-only operation, but it doesn't disclose any behavioral traits (e.g., data scope, auth needs, side effects).

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?

Very short but cryptic due to tags and Chinese text. Not effectively front-loaded; the prerequisite is noted but core purpose is missing.

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 no output schema and complex domain (RFQ trades), description is incomplete. It fails to explain what data the tool returns or how to interpret results.

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?

No parameters exist, so description does not need to add parameter info. Baseline 4 is appropriate as no additional semantics are required.

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 cryptic with tags like '[L:READ]' and 'CAT:[策略-RFQ]', and a prerequisite to call agent_catalog. Core purpose of retrieving RFQ trades is not clearly stated.

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?

Only mentions a prerequisite ('please call agent_catalog first'), but no guidance on when to use this tool vs alternatives like okx_get_rfqs.

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