prepare_kamino_supply

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

Describes the internal transaction composition (computeBudget, ATA setup, reserve refresh, etc.), decimal resolution, and validation against Kamino's main market. Adds significant detail beyond annotations (destructive, idempotent) without contradiction.

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 concise (3 sentences) but packs essential information: purpose, prerequisites, human amounts, nonce requirement, and tx composition. Front-loaded with the core action, no wasted words.

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 complexity of a Kamino supply transaction and no output schema, the description is complete: it explains the prerequisite, input validation, parameter interpretation, and what the returned transaction contains, enabling correct use.

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?

The schema already provides descriptions for all three parameters, including human amount semantics. The description adds context about market validation and prerequisite (wallet initialization) for the wallet param, complementing the schema effectively.

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 'Build a Kamino deposit (supply) tx' with specific verb and resource. It distinguishes from siblings like prepare_kamino_init_user and prepare_kamino_borrow by mentioning prerequisites and the deposit-specific flow.

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?

Explicitly tells when to use (after prepare_kamino_init_user) and what not to use (if not initialized). Also mentions required nonce and Ledger blind-sign treatment, guiding the agent on prerequisites and signing context.

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