Get Borrow Rates Info

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

With no annotations, the description carries the full burden. It discloses the key behavioral trait of being public and requiring no credentials, and 'Fetch' implies a non-mutating read. It does not mention rate limits or response format, but for a simple public data endpoint, this is adequate.

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 a single front-loaded sentence that states the action, resource, and scope. The added note about being public is concise and unnecessary words are absent.

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 zero-parameter, no-output-schema tool, the description is sufficiently complete. It explains what is fetched and that it requires no authentication. The only minor gap is no mention of what 'tiers' means or the exact response shape, but this is reasonable 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 tool has zero parameters, so according to the guidelines the baseline is 4. The description appropriately omits parameter details since there are none to describe, and the schema already reflects this with 100% 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 uses a specific verb ('Fetch') and identifies the exact resource ('borrow rates for all tiers and currencies'). It clearly distinguishes from sibling tools like 'get_borrow_status' by focusing on rates across all tiers/currencies, not a specific status.

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 context that this is a public endpoint requiring no credentials, which helps the agent know when to use it. However, it does not mention alternatives or explicitly state when not to use it, missing the full 5-level guidance.

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