hl_set_leverage

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

With no annotations provided, the description carries the full burden. It only states that leverage is set and requires authentication, but fails to disclose potential side effects (e.g., affecting open positions), rate limits, or error conditions.

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 purpose sentence, an env requirement note, and an Args block. It is front-loaded and efficient, though the Args block could be more tightly integrated.

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 3 parameters, no schema descriptions, and no annotations, the description adequately explains parameters but omits return value details (though an output schema exists). Missing information on behavioral context like prerequisites beyond env key (e.g., position existence).

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 description adds meaning beyond the bare schema: it explains coin as 'Asset symbol e.g. BTC, ETH', leverage as 'Leverage multiplier e.g. 5, 10, 20', and is_cross as 'True for cross margin, False for isolated'. This compensates for the 0% schema coverage.

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 'Set leverage for a specific asset,' which is a specific verb and resource. The tool name and description distinguish it from siblings like hl_place_order and hl_close_position, which serve different purposes.

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 mentions the prerequisite 'Requires HL_PRIVATE_KEY in env,' providing clear usage context. However, it does not explicitly state when to use this tool over alternatives or include any 'when not to use' guidance.

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