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

With no annotations, the description carries the full burden and does well: it discloses the simulation step, the rejection policy for preliminary-tx bundles, and that it returns short-lived evidence without signing. It omits auth/permission prerequisites and rate-limit or failure behavior, keeping it below a 5.

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 core intent is front-loaded in the first clause, but the sentence is a dense run-on stacking jargon ('Insight evidence for PriorSeal', 'oracle evidence') without unpacking it. Mostly earns its place, but could be split and de-jargoned.

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 an 8-required-param mutation-builder with no output schema, the behavioral narrative is thorough, but the complete absence of parameter guidance leaves a significant gap in what an agent needs to call it correctly.

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?

All 8 parameters are required with 0% schema description coverage, yet the description explains none of them. Terms like 'live vault and principal mint' loosely map to vault/assetMint, but loanSymbol, collateralSymbol, collateralValueUsd, minLpAmount, and principalAmount are never clarified, leaving most parameters undocumented in both places.

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 names a specific verb and resource ('Build a single Solana mainnet Loopscale lending-vault deposit') and enumerates the pipeline steps (verify vault/mint, resolve lookup tables, simulate, check oracle, return evidence). This clearly separates it from siblings like solana_lending_guard or pre_trade_safety_check, which check rather than build a transaction.

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?

It states clear boundaries: 'It does not sign, authorize, or broadcast' and 'Deposit bundles requiring preliminary transactions are rejected.' That is strong when-not guidance, but it never names an alternative tool to use for signing/broadcasting or for the rejected multi-step case.

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