queryFixedBorrowPenaltyInterest

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

Beyond the read-only and open-world annotations, it discloses the latest-30-day default window, descending record ordering, pagination termination, a local limit of 5 requests per rolling second, and business failures surfacing as MCP tool errors. It also clarifies authentication scope and important result-value semantics, all of which affect invocation or interpretation.

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 purpose is front-loaded, followed logically by filtering, limits, time scope, pagination, response fields, throttling, and errors. The paragraph is dense, but every sentence supplies actionable information and there is no filler.

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 four-parameter read-only query without an output schema, the description covers account scope, filters, default lookback, sorting, pagination, key response fields and their types, rate limiting, and error behavior. It provides enough detail for both an initial call and subsequent page requests, with explicit sibling routing being the only notable selection aid still missing.

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?

Despite 0% schema description coverage, the description addresses all four inputs: orderId and orderCurrency as filters, limit's range and default, and cursor's role in pagination. Although the limit details repeat structured schema constraints, the instructions to omit cursor for the default window, forward nextPageCursor unchanged, and treat an empty cursor as the final page add substantial new 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 opening sentence provides a precise verb, resource, and scope: querying fixed-rate borrow penalty interest records for the authenticated Unified account. This distinguishes the tool from siblings concerned with fixed-borrow contracts, orders, repayments, or general 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?

The description establishes a clear use case and explains optional orderId or orderCurrency filtering and cursor-based retrieval. It does not explicitly state when not to use the tool or route agents to alternatives such as getCryptoLoanFixedRepaymentHistory or getBorrowHistory.

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