waiaas_hl_get_open_orders

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

No annotations are present, so the description bears full responsibility. It discloses only the basic read operation via 'Get,' but omits details such as read-only nature, required authentication, potential errors, or behavior when no orders exist.

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 single sentence is concise and front-loaded, but it sacrifices essential information. It meets the definition of conciseness but lacks completeness, scoring moderately.

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 simple tool with two optional parameters and no output schema, the description is incomplete. It does not clarify parameter optionality, return structure, or prerequisites, leaving significant gaps for successful 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 coverage is 100%, and the schema already describes the parameters minimally. The description adds no extra meaning beyond 'for a wallet,' not explaining wallet_id format or sub_account usage. Baseline is 3 as no improvement.

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 states the specific action 'Get Hyperliquid open orders for a wallet,' clearly identifying the resource (open orders) and scope (wallet). It distinguishes from sibling tools that fetch positions or balances, though does not explicitly contrast with them.

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 is provided on when to use this tool versus alternatives like waiaas_hl_get_positions or waiaas_hl_get_trade_history. The agent must infer from the name alone, which is insufficient for proper selection.

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