getCryptoLoanFixedBorrowOrderInfo

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

No annotations provided. The description includes a rate limit (5 requests per UID), which is a useful behavioral constraint. However, it does not disclose read-only nature, idempotency, or other side effects.

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?

Extremely concise: two sentences with no redundant information. The first sentence states purpose, the second provides a key constraint (rate limit).

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 6 undocumented parameters, the description is inadequate for complete understanding. It does not explain what 'details and history' includes or how parameters affect the query.

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% with 6 parameters. The description adds no explanation of what each parameter does, leaving the agent to infer from parameter names alone.

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 verb 'Query' and the resource 'borrow order details and history'. While it doesn't explicitly mention 'fixed borrow', the tool name provides that context. It distinguishes from siblings like getBorrowHistory but not from queryFixedBorrowOrders.

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 on when to use this tool vs alternatives like queryFixedBorrowOrders or getBorrowHistory. No prerequisites or exclusions mentioned.

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