write_account_borrow

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

Adds real behavioral context beyond the annotations: the output is an unsigned transaction rather than an executed borrow, the tool performs validation and rejects spot accounts, and only margin accounts with a creditor qualify. Annotations already cover safety/idempotency, so this is strong complementary disclosure, though it doesn't mention the subsequent signing/submission step or what happens on insufficient margin beyond rejection.

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?

Four tight sentences, front-loaded with the core action, then exclusions, then prerequisites. Every sentence carries actionable information with no filler or repetition of the schema.

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 transaction-building tool with an output schema and full annotation coverage, the description supplies everything an agent needs: what it builds, which account types qualify, what it rejects, which sibling to use instead, and the pre-call verification step.

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 coverage is 100%, so the baseline is 3; the description adds meaning by tying account_address to collateral semantics and referencing the read_account_info fields (collateral_value, used_margin) an agent must check before choosing an amount. It does not add syntax or format detail for amount/pool_address, but the schema handles those.

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?

Opens with a specific verb and resource: 'Build an unsigned transaction to borrow from an Arcadia lending pool against account collateral.' It immediately differentiates itself from the closest sibling (write_account_add_liquidity) that could otherwise be confused for the same borrowing behavior.

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 states when NOT to use it ('NOT needed for leveraged LP: write_account_add_liquidity handles borrowing internally when leverage > 0') and names the alternative. It also gives a pre-call workflow: verify positive free margin via read_account_info, with the concrete condition (collateral_value must exceed used_margin).

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