okx_amend_batch_orders

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

No annotations are provided, so the description must disclose behavioral traits. The description only has a label indicating write operation but does not mention authentication needs, destructive nature, rate limits, error conditions, or other important behaviors. This is severely lacking.

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 extremely short but at the expense of utility. It is not concise in a helpful sense; it is under-specified and missing critical information. A useful description would be longer but still concise.

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 (write operation, batch processing, JSON parameter, no output schema), the description is completely inadequate. It does not explain return values, error handling, or any success/failure indicators. The agent would be left guessing about the tool's behavior.

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 single parameter 'orders' has a detailed description in the schema, including an example and maximum count. The description itself does not add extra semantics beyond the schema, so a baseline score of 3 is appropriate.

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: only contains a label '[L:WRITE]' and a note to call agent_catalog first. It does not explicitly state that this tool amends batch orders. The parameter description in the schema hints at the purpose, but the description itself is insufficient.

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?

No guidance provided on when to use this tool versus alternatives like okx_amend_order (single amend) or okx_batch_cancel_orders. The description does not mention any prerequisites, context, or exclusions.

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