spotMarginSetLeverage

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

Annotations already indicate this is a mutating, non-destructive operation. The description adds useful context beyond annotations by giving a valid leverage range and the activation prerequisite. It does not disclose side effects like whether existing orders are affected, but the annotations reduce the burden.

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 two concise sentences: the first states the action and scope, the second gives the prerequisite and constraint. Every sentence adds useful information with no redundant 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?

The description gives the core purpose, a prerequisite, and a valid range, which is solid for a simple two-parameter tool. However, it omits any explanation of the optional 'currency' parameter and does not clarify whether omitting it is typical or requires special conditions. This leaves a notable gap for correct 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?

The description explains that leverage must be between 2 and 10, which adds meaning to that parameter. However, schema description coverage is 0%, and the optional 'currency' parameter is not explained at all—neither its purpose nor what happens if omitted. The description only partially compensates for the bare 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 the specific action ('Set'), the resource ('maximum leverage'), and the domain ('spot cross margin trading'). It implicitly distinguishes this from the sibling setLeverage tool, which likely covers non-spot or derivatives leverage.

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 provides a clear prerequisite: the account must have spot margin activated first. It also implicitly scopes usage to spot cross margin. However, it does not explicitly mention when not to use it or name alternative tools such as setLeverage or spotMarginSwitchMode.

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