getCryptoLoanFlexibleBorrowHistory

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

Provides rate limit (5 requests per UID), which is helpful. No annotations exist, so description carries full burden. Missing details on data freshness, read-only nature, or side effects. Adequate but not thorough.

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?

Single sentence plus bullet points. Efficiently front-loads purpose. Every line adds value. No redundancy.

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?

Missing output schema and parameter descriptions. With 4 optional parameters and no annotations, description should clarify default behavior, return format, and pagination intricacies. Partially covered by feature list.

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 0%, so description must compensate. It mentions query by order ID or currency and pagination, mapping to parameters loosely, but fails to explain input formats, valid values, or cursor mechanics. Minimal added meaning.

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 action ('Query') and the resource ('historical flexible borrow records') with pagination. It differentiates from siblings like getCryptoLoanFlexibleRepaymentHistory by specifying 'borrow history'.

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?

No explicit guidance on when to use this tool versus alternatives like getCryptoLoanFlexibleOngoingCoin. The rate limit mention is a constraint but not usage direction. Missing 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.