setAutoAddMargin

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

No annotations provided, so description carries full burden. Discloses that it automatically adds margin from available balance to prevent liquidation, works only in isolated margin mode, and requires linear contracts. However, it does not mention side effects (e.g., consumption of balance) or authorization requirements.

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?

Two paragraphs: first paragraph states purpose and conditions, second paragraph is an agent hint with usage details. Front-loaded, no fluff. Could integrate hint into first paragraph but still well-structured.

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 the tool is a simple toggle with no output schema, the description covers main points: what it does, when it works, and parameter meanings. Does not elaborate on immediate effects or compare to related tools, but sufficient for a low-complexity tool.

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 description coverage is 0%, so description must compensate. It explains autoAddMargin values (1 enable, 0 disable) and positionIdx meaning (1=buy, 2=sell in hedge mode). But it does not explain 'category' (only linear) or 'symbol' format. Adds value for 2 of 4 parameters.

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 toggles the auto-add-margin feature for a position, includes specific verb 'toggle', resource 'auto-add-margin feature', and constraints (isolated margin mode). It distinguishes from siblings like 'addMargin' or 'addReduceMargin' which are different operations.

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?

Explicitly says 'Use this to toggle auto-add-margin on isolated margin positions' and specifies parameter settings for enable/disable and hedge mode. Does not explicitly list alternatives, but provides clear context for when to use.

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