hl_place_order

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

The description discloses the need for HL_PRIVATE_KEY and the reduce_only behavior, but does not explain side effects (e.g., fund deduction) or what the tool returns. With no annotations, more behavioral context would be beneficial.

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 concise with a clear 'Args:' section. Each sentence serves a purpose, though the overall structure could be more front-loaded with a stronger summary.

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 complexity (6 parameters, trading context) and the presence of an output schema, the description covers the key inputs but lacks details on output, error handling, and trading risks. It is adequate but not fully comprehensive.

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?

Despite 0% schema description coverage, the description provides meaningful explanations for each parameter (e.g., 'True for long/buy, False for short/sell', 'None for market order'), adding significant value beyond the schema types and defaults.

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 'Place an order on Hyperliquid' with a specific verb and resource. It lists all parameters and their meanings, and the tool name and sibling names help distinguish it from order cancellation and position management tools.

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 does not provide when or when not to use this tool versus alternatives like limit vs market orders, or compared to other order-related siblings. It mentions authentication but lacks explicit guidance on context.

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