spotMarginSetLeverage

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

No annotations are provided, so the description carries the burden. It states the tool sets maximum leverage (mutation) and includes a prerequisite and range. However, it omits potential side effects, permissions, or rate limits, which are common for mutation tools.

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, with no fluff. The first states the purpose, the second adds conditions, making it efficient and easy to parse.

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 output schema, the description should explain return values, but does not. The currency parameter is also unexplained. However, the tool is simple and the description covers core usage, so it is partially complete.

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 schema has 2 parameters with 0% description coverage. The description adds meaning to 'leverage' by specifying a valid range (2-10), but does not explain the 'currency' parameter at all, leaving it ambiguous.

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 tool sets maximum leverage for spot cross margin trading, specifying the action, context, and prerequisite. It distinguishes from siblings like 'setLeverage' by focusing on spot cross margin.

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 (spot margin activated) and valid leverage range (2-10), providing clear context. It does not explicitly state when not to use or compare to alternatives, but the given information is sufficient for basic usage.

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