okx_amend_spread_order

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

With no annotations, the description carries full burden for behavioral disclosure. The 'L:WRITE' tag implies mutation, but no side effects, permissions, or return behavior are mentioned. The prerequisite is the only additional context.

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 very short, which is concise, but lacks substantive information. It front-loads tags and a prerequisite but does not earn its place with clear utility.

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?

As a mutation tool with no annotations or output schema, the description is incomplete. It omits return value, confirmation, or any system state changes, leaving the agent without sufficient context for correct invocation.

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?

The input schema has 100% coverage with Chinese parameter descriptions, so the description does not need to repeat them. However, it adds no cross-references or usage hints for parameters, achieving only the baseline for full schema coverage.

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 does not explicitly state that the tool amends a spread order; it only provides a category tag and a prerequisite note. The tool name suggests the purpose, but the description adds no clarifying verb or explanation.

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 includes a prerequisite ('请先调用 agent_catalog') but offers no guidance on when to use this tool versus alternatives like okx_place_spread_order or okx_cancel_spread_order. No exclusions or context are provided.

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