set_leverage

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

Annotations already indicate destructiveHint=true. The description adds that the operation is 'HIGH risk' and 'requires confirmation', which provides useful behavioral context beyond annotations. However, other traits like idempotency or effect on existing positions are not mentioned.

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 one header line and a structured parameter list. It is front-loaded with the risk warning and parameter details. However, the parameter list could be more tightly integrated into a single sentence.

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?

The output schema exists but is not referenced. The description covers the basic action and parameters but lacks details on error scenarios, confirmation flow, or impact on existing positions. Given the destructive nature, more context would be beneficial.

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 0%, but the description provides meaning for all parameters: category type, symbol name, leverage ranges (0 to max for risk limit). This adds significant value beyond the raw schema fields, though it does not specify exact allowed values or format.

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 specifies 'Set leverage for a position' which clearly identifies the action and resource. It is distinct from sibling tools like set_trading_stop or set_auto_add_margin which have 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 warning 'HIGH risk - requires confirmation' implies careful use but does not explicitly state when to use or when to avoid this tool. No alternative tools are mentioned. The guidance is minimal but not misleading.

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