get_new_crypto_loan_flexible_borrow_history

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

With no annotations provided, the description must fully convey behavioral traits. It only states 'Get history' without disclosing return format, authentication requirements, rate limits, pagination, or error conditions. This is insufficient for safe agent invocation.

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 minimal and well-structured, with clear labels for arguments. Every sentence serves a purpose, and the entire description is front-loaded.

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 simple retrieval tool with two optional parameters, the description covers the basic purpose and parameters. However, the absence of output schema and behavioral notes leaves gaps, especially compared to sibling tools with more detailed descriptions.

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 has 0% description coverage, so the description adds value by explaining loan_currency as a filter and limit as record count with default. However, it lacks details like valid currency formats or limit boundaries.

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 'Get flexible crypto loan borrowing history', which indicates the resource and operation. However, it does not explicitly differentiate from siblings like get_new_crypto_loan_flexible_loans or get_crypto_loan_borrow_history, though the tool name itself provides some distinction.

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 guidance is provided on when to use this tool versus alternatives. Given the extensive list of sibling tools (e.g., get_new_crypto_loan_flexible_loans, get_new_crypto_loan_flexible_repay_history), the description lacks context about use cases or prerequisites.

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