deposit_to_strategy

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

With no annotations, the description carries the full burden of behavioral disclosure. It states 'Deposit funds' but does not disclose that this executes an on-chain transaction, entails gas costs, is likely irreversible, or requires user wallet authorization. This is a significant gap for a financial mutation 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, clear, front-loaded sentence with no redundant or filler content. It efficiently conveys the core action and target, making it appropriately concise for its limited scope.

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?

This is a complex financial transaction tool with no output schema and no annotations. The description is minimal and does not cover important contextual aspects such as transaction finality, the need for gas/slippage configuration, or the existence of a simulation tool. It is under-specified for the task.

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 coverage is 100% with descriptions for all parameters (amount, gasLimit, slippage, strategyId, walletAddress). The description adds no parameter-level insights beyond the schema, so the baseline of 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 action ('Deposit funds') and target ('specific DeFi strategy on Puffer Finance'), making the tool's purpose obvious. However, it doesn't explicitly differentiate from the sibling tool 'simulate_deposit', which could be confused as a deposit action, though the verb 'simulate' vs 'deposit' provides some implicit distinction.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as needing to fetch strategies first, or suggest using 'simulate_deposit' before executing a real deposit. There is no contextual instruction at all.

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