getBorrowHistory

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

No annotations are provided, so the description carries the burden. It discloses rate limit, default behavior, pagination limits, and max time span. It does not mention read-only nature or effects on state, but as a query tool this is acceptable.

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 very concise: three short paragraphs for purpose, rate limit, and agent hints. No fluff, front-loaded with key information, and easy to parse.

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?

There is no output schema, and the description does not describe the return values or structure. While it explains parameters and usage well, it omits what the response contains, leaving some uncertainty for the agent.

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?

Parameter schema coverage is 0%, but the description adds meaning beyond the raw schema: it mentions filtering by currency (with examples), time range, and pagination via cursor and limit. It also explains defaults and constraints, compensating for the low schema coverage.

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 it queries interest and borrowing records for the unified account, with filtering and pagination. It distinguishes from siblings by specifying the scope, but does not explicitly differentiate from similar borrowing history tools.

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 agent hint explicitly states when to use it ('review borrowing costs and interest history'), provides currency examples, and mentions default time range and max span. It lacks explicit contraindications or alternative tools.

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