Deposit Asset To A Sui Vault

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

Annotations are empty, so the description carries the full burden. It only says 'deposit', which implies a write operation, but gives no details on side effects, reversibility, prerequisites, or how funds are handled. Minimal transparency beyond the tool name.

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, compact sentence with no filler or redundancy. It is appropriately front-loaded and earns its place.

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?

Without an output schema or annotations, this 5-parameter transactional tool needs richer context. The description does not explain expected return values, the relationship between amountUsd and amountNative, or what constitutes a 'USD-equivalent asset'. It is inadequate for safe invocation.

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 each parameter is already documented. The description adds no parameter-specific context, but the high schema coverage means it does not need to compensate. Baseline 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 clearly states a deposit action on a vault, with an explicit chain qualifier 'Sui/SUI-chain' that distinguishes it from sibling tools for Solana/EVM. However, the phrase 'certain USD-equivalent asset' is vague about which asset is involved.

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 use for Sui vaults via the chain qualifier, which is clear context. It does not explicitly mention alternatives or exclusions, but the chain-specific wording is sufficient to differentiate from other deposit tools.

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