prepare_kamino_init_user

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

Beyond annotations (readOnlyHint=false, destructiveHint=true, idempotentHint=true), the description adds critical behavioral context: the specific accounts created and their rent costs, that it refuses if already initialized, the need for a durable nonce, and blind-sign instructions for Ledger. No contradictions with annotations.

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 front-loaded with the core purpose and then provides detailed context. While every sentence adds value, the length is slightly above minimal. However, it avoids redundancy and is well-structured for an AI agent.

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 no output schema, the description explains the return value (created accounts and their costs), prerequisites (durable nonce), and failure conditions (already exists). It covers all needed context for correct invocation without omitting critical information.

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 single parameter 'wallet' has 100% schema coverage. The description enhances it by explaining why the wallet is needed (funds LUT rent) and the prerequisite of having an initialized durable-nonce account. This adds meaning beyond the schema's base64 pattern validation.

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 it is for first-time Kamino setup, creating specific PDAs (user lookup table, userMetadata, obligation) in a single transaction. It explicitly distinguishes itself from sibling tools like prepare_kamino_supply/borrow/withdraw/repay by positioning it as a one-time required prerequisite.

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?

Provides explicit usage guidelines: one-time setup, required before using supply/borrow/withdraw/repay tools. States that it refuses if userMetadata already exists, telling agents to use supply directly. Mentions requirements (durable nonce, blind-sign on Ledger) and costs (0.028 SOL rent).

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