postCryptoLoanFlexibleBorrow

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

No annotations are provided, so the description carries full burden. It discloses key behaviors: private endpoint (authentication), hourly floating rate, repay anytime, interest calculated hourly, multiple collateral support, and rate limit. Important notes about LTV and checking rates add transparency. Could mention if loan is immediately disbursed.

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 well-structured with clear sections (Features, Use Cases, Important). Every sentence provides value, and the length is appropriate for the tool's complexity. No redundant or vague statements.

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?

The description references other endpoints (loanable-data) and provides enough context for a borrowing tool. However, it lacks output details (what is returned) and does not cover error cases or prerequisites beyond LTV. Given no output schema, more completeness would be beneficial.

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?

With 0% schema description coverage, the description must explain parameters. It mentions loanCurrency, loanAmount, and collateralList only as parameter names without format, constraints, or examples. The 'Important' note about LTV hints at their use but does not detail parameter semantics.

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 'Borrow crypto with flexible hourly interest rates.' It specifies the action (borrow), resource (crypto loan), and key differentiator (flexible vs. fixed, hourly rates). This distinguishes it from sibling tools like postCryptoLoanFixedBorrow.

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 'Use Cases' section provides clear scenarios: short-term borrowing, avoiding fixed-term commitment, and leveraging hourly rate changes. It also advises checking loanable-data for current rates. However, it does not explicitly state when not to use or compare with fixed borrowing.

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