blockrun_defi

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

No annotations provided, so description carries full burden. It discloses that calls are GET only, pricing per path (in USDC), no API key needed, and notes that the yields response is large (suggesting client-side filtering). No contradictions.

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?

Description is well-structured: summary line, bulleted list of paths with costs, two example invocations, and sibling guidance. Every sentence provides unique value, no redundancy. 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?

Given the tool's moderate complexity (multiple endpoints, pricing, no output schema), the description covers most needs: what each endpoint returns, costs, and basic usage. However, it does not describe the structure of responses (e.g., JSON format, fields), which could be helpful but is not critical since output schema is absent and endpoints are well-known (DefiLlama).

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?

Input schema covers both parameters (path, agent_id) with 100% coverage. Description adds significant meaning: lists exact path suffixes with examples, explains price formatting (e.g., 'base:0x833589...,coingecko:ethereum'), and provides cost per endpoint. This goes beyond 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 explicitly states the tool provides DeFi fundamentals via DefiLlama, listing specific endpoints (protocols, chains, yields, prices). It clearly distinguishes from siblings like blockrun_price and blockrun_dex by contrasting their purposes ('plain spot quotes', 'DEX pairs').

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 guidance: 'Use blockrun_price (free) for plain spot quotes, blockrun_dex (free) for DEX pairs, blockrun_surf for labeled on-chain data — this tool is for protocol/TVL/yield fundamentals.' Also includes examples showing correct usage patterns.

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