Get Borrow Status

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

With no annotations provided, the description carries full burden. It discloses a critical prerequisite (POLONIEX_API_KEY and POLONIEX_API_SECRET environment variables) and clarifies the optional-parameter behavior. It also indicates the returned data fields, giving the agent an idea of what to expect, though it does not describe error cases or output format beyond that.

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 concise sentences; the first states the core purpose and output data, and the second addresses the optional parameter and authentication requirement. It is front-loaded and contains 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 simple read-only tool with one optional parameter and no output schema, the description covers the essential aspects: purpose, returned data, parameter usage, and authentication. It does not explain the exact response structure or error handling, but these gaps are acceptable given the tool's simplicity.

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 input schema already fully describes the `currency` parameter (filter by currency, omit for all), and the description repeats this same guidance without adding new semantic detail. Since schema coverage is 100%, the description provides minimal added value for parameters.

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 tool's function with a specific verb ('Fetch') and resource ('borrow status for margin currencies'), listing the returned data elements (borrowed amounts, rates, available amounts). This distinguishes it from sibling tools like get_borrow_rates_info or get_account_margin by its scope and output details.

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 provides clear usage context, noting that omitting `currency` returns all margin currencies, but it does not explicitly name alternatives or state when not to use this tool compared to siblings. The context is clear enough for basic usage.

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