adjust_isolated_margin

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

Discloses failure conditions (MarginModeNotIsolated, NoOpenPosition, margin floor), requires API credentials, and explicitly states 'moves REAL margin'. No annotations present, so description carries full burden and meets it.

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 sentences: first covers purpose and failure conditions, second clarifies amount format and requirements. Efficient and front-loaded with key information.

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?

Covers purpose, failure modes, parameter format, and real impact. No output schema, so return value is not addressed. For a 3-parameter tool with no annotations, provides sufficient completeness.

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 100%, so baseline is 3. Description adds that 'amount' is a positive decimal string, which matches schema. No significant additional meaning beyond what schema provides.

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?

Clearly states action (add/remove isolated margin), resource (margin on open position), and distinguishes from siblings like deposit_collateral. Includes failure conditions indicating scope.

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?

Provides failure modes but does not explicitly state when to use this tool vs alternatives like deposit_collateral. Implies usage context but lacks explicit guidance.

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