prepare_marginfi_borrow

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

Discloses that tool builds unsigned transaction, includes pre-flight checks, SDK computes oracle-refresh, health-factor gate enforced on-chain, and BLIND-SIGN on Ledger. Adds value beyond annotations.

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?

Multiple sentences but each adds value. Slightly longer but well-structured and front-loaded with key info.

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, behavior, prerequisites, parameter nuances, and Ledger note. No missing context given no output schema. Complete for a borrow transaction builder.

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?

All 5 parameters have schema descriptions. Description adds meaning: symbol resolution to mint, SOL/wSOL handling, accountIndex default, and human-readable amount. No gaps.

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?

Explicitly states 'Build an unsigned MarginFi BORROW tx', including pre-flight checks and prerequisites. Clearly distinguishes from sibling tools like prepare_marginfi_supply.

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?

Mentions prerequisites (durable nonce, prepare_marginfi_init), advises using mint if token not in canonical list, and explains pre-flight refuses on zero collateral. Implicitly warns against use when no collateral available.

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