getCryptoLoanFixedRenewInfo

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

The description includes a rate limit annotation ('5 requests per UID'), which adds behavioral context beyond the schema. However, it does not disclose read-only nature or pagination behavior implied by limit and cursor parameters.

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 two sentences, including the rate limit note, with no unnecessary words. It is appropriately sized for a simple query tool.

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?

Given no output schema and 0% parameter coverage, the description is incomplete. It does not explain return values or how to use parameters effectively, leaving significant gaps for a 4-parameter tool.

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 description coverage is 0%, and the description does not explain any of the four parameters (orderId, orderCurrency, limit, cursor). It fails to add meaning beyond the schema.

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 loan renewal history and information', specifying the resource (loan renewal) and action (query). It distinguishes from sibling tools like getCryptoLoanFixedBorrowContractInfo by focusing on renewal.

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 other crypto loan query tools or alternatives. The description does not mention context or exclusions.

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