get_borrows

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

The description adds only the adjective 'recent' beyond the annotations' readOnlyHint. It does not disclose data freshness, pagination, rate limits, or any behavioral traits. Annotations already provide readOnlyHint, so the description adds minimal value.

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, clear sentence with no wasted words. It could benefit from slightly more structure (e.g., stating the output), but it is appropriately concise for a simple tool.

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?

With 5 parameters (including enums for protocol and network) and no output schema, the description is too brief. It does not explain what 'recent' means, how to interpret events, or provide any guidance on using the optional parameters effectively. This leaves significant gaps for an AI 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?

Schema description coverage is 100%, so the schema already documents all parameters. The description mentions filtering by market ID and account, which matches the schema but adds no new meaning beyond what the schema provides. Baseline 3 is appropriate.

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 returns 'Recent borrow events' and specifies optional filters by market ID and account address. This directly distinguishes it from sibling tools like get_deposits, get_liquidations, etc.

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 implies usage for retrieving borrow events with optional filters, but does not explicitly state when to use this tool versus alternatives, nor provide any when-not guidance. The context of sibling tool names partially implies differentiation.

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