get_lending_rates

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

No annotations are provided, so the description carries the behavioral disclosure burden. 'Get current' implies a read-only retrieval with no side effects, but the description does not explicitly confirm read-only behavior, authentication needs, or whether rates are live vs. cached. This is a modest gap for a getter tool.

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 with no filler. Every word contributes meaning, specifying both what is retrieved and the protocol context.

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 tool with one optional, fully documented parameter and a simple read operation, the description plus schema is sufficient for correct invocation. The absence of an output schema means return format is unknown, but the description does not need to enumerate return values; overall it is complete for 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 has 100% description coverage, with the asset parameter clearly explained as optional and returning all assets if not specified. The tool description itself adds no parameter-level detail, but the schema already handles this, so the baseline of 3 applies.

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 clear verb ('Get') and identifies a specific resource ('current borrow and supply rates on Burrow lending protocol'). It is distinguishable from sibling tools by naming Burrow and the specific rate types, though it does not explicitly contrast with get_defi_yields.

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?

Usage context is implied: use this when you need current Burrow borrow or supply rates. However, it does not explicitly state when not to use it or mention alternatives like get_defi_yields for broader DeFi yield comparisons.

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