analyze_treasury_health

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

No annotations provided, so description carries full burden. Discloses analysis scope and optional computation, but does not explicitly state that the tool is read-only or has no side effects. Adequate but could be more precise.

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?

Two concise sentences, front-loaded with key purpose, specific metrics, and actionable context. No redundant or unnecessary 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?

Covers main outputs (balances, gas, runway, recommendation) despite no output schema. Lacks detail on return format or error handling, but sufficient for a single-function analysis 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 covers parameters 100% with descriptions. Description adds value by explaining that daily_burn_usd enables days of runway and rebalance recommendation, beyond schema details.

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?

Clear verb 'Analyze' and specific resource 'agent wallet's treasury health'. Lists exact metrics (GBLIN/USDC/ETH balances, gas runway, days of runway, rebalance recommendation), distinguishing it from sibling tools like get_treasury_state or swap tools.

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?

States 'Critical for autonomous decision-making,' implying when to use. Does not explicitly exclude scenarios or name alternatives, but sibling context (analysis vs. actions) provides clarity.

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