get_kamino_positions

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds value beyond annotations by explaining empty list for wallet with no Kamino userMetadata, health factor convention, and reserve-level warnings. No 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 a single dense paragraph but front-loaded with 'READ-ONLY' and the main purpose. Every sentence provides necessary detail. Slightly dense but not excessive.

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?

The tool has no output schema, so the description fully explains return values: obligation PDA, per-reserve details, totals, health factor, and edge case of empty list. Annotations cover safety. Complete for a read-only query tool.

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% for the single parameter 'wallet'. The tool description does not add significant extra meaning for the parameter beyond what the schema provides. Baseline 3 applies per guidelines.

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 enumerates a Solana wallet's Kamino lending position on the main market, with specific verb 'enumerate' and resource defined. It distinguishes from sibling tools like get_marginfi_positions by explicitly naming Kamino and main market.

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?

While the description implies use for Kamino positions, it does not explicitly state when to use this tool over alternatives or provide exclusions. The name and context make it clear for Kamino queries, but no when-not-to-use guidance is given.

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