getCryptoLoanFlexibleOngoingCoin

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

The description declares it as a query (read-only) and mentions a rate limit of 5 requests per UID. With no annotations, this provides useful behavioral info, but it omits details like authentication requirements or whether data is real-time.

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 concise (4 lines) and well-structured with a headline, features list, and use cases. Every sentence adds value, with no unnecessary text.

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 query tool with no output schema and one optional parameter, the description covers purpose, features, use cases, and rate limit. It lacks response format details but is adequate for basic understanding.

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?

The only parameter, 'loanCurrency', is implied by 'by currency' but lacks format, allowed values, or examples. With 0% schema coverage, the description should compensate more, but only gives minimal context.

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 'Query current flexible borrow positions by currency' and lists specific features like viewing debt, interest, and hourly rate. It distinguishes from siblings by focusing on current positions, as opposed to history tools like getCryptoLoanFlexibleBorrowHistory.

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 explicit scenarios (e.g., check debt amount, monitor interest, calculate repayment). However, it does not explicitly contrast with sibling tools or state when not to use it, though the context is clear enough.

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