setMarginMode

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

With no annotations, the description carries the full burden. It discloses the rate limit (5 req/s), that it returns failure reasons, and that portfolio margin has a minimum equity requirement. It could mention idempotency or effects on existing positions, but the provided info is solid.

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 very concise with four sentences covering purpose, parameters, rate limit, and hints. No wasted words; everything is front-loaded and relevant.

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?

For a simple tool with one parameter and no output schema, the description covers all key aspects: what it does, what modes are available, rate limit, failure handling, and prerequisites (portfolio min equity). It is complete for effective use.

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 single parameter setMarginMode is well-covered by the schema (enum with three options). However, the description only repeats that it's required and does not add any additional meaning about what each mode implies (e.g., risk profiles, eligibility). With 0% schema description coverage, the description should compensate, but it doesn't.

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 the account margin mode and lists the three supported modes (ISOLATED_MARGIN, REGULAR_MARGIN, PORTFOLIO_MARGIN). It distinguishes itself from sibling tools like setLeverage and setHedgingMode by focusing specifically on margin mode.

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 explicitly states when to use the tool ('to change the account's margin mode') and provides actionable hints: check result.reasons for failures, note portfolio margin requires equity threshold, and suggests calling getAccountInfo first to check current mode. This covers both when and when-not to use.

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