agent_quick_trade

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

No annotations provided; description discloses it is a WRITE operation (real order), requires API key with trade permission, and returns ~1KB data. Does not detail side effects beyond placing order, but sufficient.

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 structured with headings and bullet points, front-loading function and scenario. Some redundancy but overall clear and easy to parse.

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?

Covers function, scenario, parameters, auth, risk, return size, and related tools. Without output schema, explains return includes precheck results, order confirmation, and risk reminders. Complete for a multi-step tool.

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 100% so baseline 3. Description adds Chinese translations, notes optional px, default ordType, and explains parameters in context of quick trade, adding value beyond 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 clearly states it performs a one-step trade with automatic balance, max quantity, price limit checks, and order placement, returning structured confirmation. Distinguishes itself from separate tools like okx_place_order.

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?

Explicitly says to call when user says 'buy 0.1 BTC' and that no need to call separate tools. Lacks explicit when-not conditions, but context is clear.

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