bybit_amend_order

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

Without annotations, the description must disclose behavioral traits, but it only says 'Amend an order'. It omits important details like what happens if the order doesn't exist, whether partial amendments are allowed, or if there are any restrictions on changing specific fields.

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 concise with a single sentence, but this comes at the cost of necessary detail. It is appropriately front-loaded, yet too minimal to be helpful.

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 complexity of 6 parameters (2 required) and no output schema, the description is completely inadequate. It fails to explain input requirements, behavior, or return values, making it unreliable for correct tool 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?

Schema description coverage is 0%, and the description adds no meaning to any parameters. It does not explain the purpose of fields like 'qty', 'price', 'orderId', or the 'category' enum values, leaving the agent to guess their roles.

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 clearly states the action ('Amend') and the resource ('an order on Bybit V5'), making the tool's purpose immediately understandable. However, it lacks differentiation from sibling tools like bybit_cancel_order or bybit_place_order, which could cause confusion about when to use this specific tool.

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 usage guidelines are provided. The description does not indicate when to use amend over alternatives (e.g., cancel and re-place), nor does it mention any prerequisites or context such as order status requirements.

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