set_leverage

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

No annotations are present, so the description carries the full burden. It discloses support for isolated/cross margin but omits behavioral traits such as persistence across sessions, effects on existing positions, required permissions, or error conditions. As a mutation tool, these details are important.

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 two short sentences that front-load the action and provide a clarifying example. Every word adds value, and there is no redundancy or filler.

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 no annotations and no output schema, the description should provide more context about return values, prerequisites, and side effects. It does not mention what happens after setting leverage, how positionSide interacts, or potential errors. The description is a minimal viable but leaves significant gaps for an agent.

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?

With 0% schema coverage, the description partially compensates by illustrating the symbol format (BTC/USDT:USDT) and leverage value (10x), and explicitly mentions isolated/cross margin, which maps to marginType. However, positionSide is not explained, so the parameter semantics are incomplete.

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 a specific verb ('Set leverage') and resource ('perpetual futures trading'), with an example that clarifies the symbol format and leverage values. It clearly distinguishes from sibling tools like get_leverage (read vs. write) and place_order (order placement vs. leverage configuration).

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 explicit when-to-use or when-not-to-use guidance is provided. The description implies it is for setting leverage before trading but does not mention alternatives or preconditions. Sibling tools like get_leverage or place_order are not referenced.

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