defi-state-pack

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

With no annotations, the description carries full burden. It discloses supported chains, free upstreams (DRPC, DeFiLlama), no API key needed, and filtering options. It does not mention rate limits or error handling, but provides good insight into the tool's behavior.

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, front-loaded with the core purpose, then benefit, then supported chains and filters. Every sentence adds value with no wasted 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?

For a 10-parameter composite tool with no output schema, the description covers the main purpose, data sources, and filters. It does not detail return structure or pagination, but is comprehensive enough for an AI agent to use effectively.

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 coverage is 100%, baseline 3. The description adds value by explaining filter semantics in context (e.g., case-insensitivity, default min TVL of $1M, and max top_pools of 25). This goes beyond the schema's individual parameter 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 returns Ethereum block header, stablecoin depeg status, and top DeFi yield farming pools in one call. It explicitly mentions collapsing a 3-hop chain, distinguishing it from individual sibling tools like eth-block, stablecoin-watch, and defi-yields.

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?

The description explains the composite nature and parallel fetching, implying it's for when all three data types are needed. It does not explicitly state when not to use or compare to alternatives, but the context is clear enough for an agent.

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