prepare_kamino_supply

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

Discloses important behaviors: refusal if not initialized, mint validation, decimal resolution, durable nonce requirement, blind-sign treatment, and transaction composition. These go well beyond the annotations which only provide destructive and idempotent hints.

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?

Four sentences, each packed with relevant information: purpose, constraints, input handling, and tx details. No wasted words, front-loaded with core purpose.

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?

Covers prerequisites, validation, input format, nonce, and tx structure. Lacks output format details, but given no output schema, the description reasonably implies a transaction object. Slight gap in specifying that the tool returns a serialized transaction.

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?

Each schema parameter is enriched with additional context: wallet must have run init user, mint must be listed with common examples, amount is human-readable with decimal resolution explained. This adds value beyond the schema descriptions.

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 tool builds a Kamino deposit transaction, distinguishes it from sibling tools like prepare_kamino_init_user by noting the prerequisite and validation conditions, and uses specific verb-resource pairing.

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 says to run prepare_kamino_init_user first, and validates mint listing. Provides good context on when to use, though does not directly compare with other Kamino tools beyond prerequisites.

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