haiku_analyze_portfolio

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

No annotations provided, so description carries full burden. It discloses that the tool returns enriched positions with APY, health factors, and context-specific opportunities. While it doesn't detail side effects (likely none as it's read-only), the description is clear and trustworthy. Minor gap: doesn't explicitly state it's read-only.

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?

Three sentences, all informative. The first sentence states purpose and returns, the second gives usage guidance, the third provides workflow integration. Efficient and well-structured. Slight redundancy with 'context-specific opportunities' could be trimmed.

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 simple input (one string) and no output schema, the description fully covers what the tool does, returns, and how it fits into a workflow. No missing information for an agent to use it correctly.

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 'walletAddress', and the description already implies it's a wallet address. The description adds value by explaining the output is based on what the wallet holds, but the parameter itself is straightforward.

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 analyzes a wallet's DeFi portfolio and surfaces yield opportunities, specifying what it returns (positions, APY options, health factors, opportunities). It uses specific verbs ('Analyze', 'surface') and distinguishes itself from sibling tools like haiku_discover_yields and haiku_execute.

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 states when to use ('when a user asks what they should do with their portfolio or wants yield optimization advice') and provides clear guidance on pairing with haiku_discover_yields for market context and haiku_get_quote for execution. No exclusions needed.

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