Lends Prepare Deposit

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds some value by indicating that the tool constructs a transaction rather than executing or submitting one, but it does not disclose additional behavioral details such as return format or prerequisites.

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 earns its place, and it is appropriately sized for a simple two-parameter tool whose schema already defines the allowed values.

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?

Given the low complexity (two parameters, no output schema, no nested objects), the description is minimally adequate: it states that the tool constructs a transaction and the schema defines the parameter shapes. However, it omits return-value expectations and leaves parameter semantics implicit, so an agent must infer some invocation details from the names alone.

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 0%, so the description must compensate by explaining the parameters. It does not: "collateral" and "amount" are left to their names and schema patterns, with no clarification of units, token decimals, or how the amount relates to the collateral asset.

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 and resource: "Construct a collateral deposit transaction." It clearly distinguishes this from the many sibling tools (e.g., prepare_withdraw, prepare_borrow) by naming the deposit operation, and there is no ambiguity about what the tool produces.

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 intended use is implied: use this when you need to construct a collateral deposit transaction. However, there is no explicit guidance about when not to use it or which sibling prepare_* tool to choose instead, leaving the agent to infer the selection from names and context.

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