hl_build_order

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

Discloses key behaviors: non-custodial (returns action+nonce for signing), minimal fee, and that it builds an order action. Annotations (readOnlyHint=false, destructiveHint=false) are consistent with description. No contradictions.

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?

Two sentences, no wasted words. Front-loaded with the core action and fee, followed by essential workflow. Perfectly 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?

For a tool with 6 parameters and no output schema, the description covers the workflow (approve, build, sign, post), return format, and fee. Agent can fully understand how to use it.

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 is 100%, so description need not repeat parameter details. It adds value by explaining the return format (action + nonce) and the minimal fee, which provides context beyond the 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?

The description clearly states 'Build a ready Hyperliquid perpetual order action' with specific details (SwapTitan builder code, minimal 0.001% fee). It distinguishes itself from sibling tools like evm_swap and sol_swap by specifying the Hyperliquid context and non-custodial nature.

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 instructs to call hl_approve first (once) and describes the signing and posting steps. Provides clear usage context, though it doesn't explicitly mention when not to use or alternatives.

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