barker_defi_vaults

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

Explains the output format, including that supply_apy_total is a decimal to multiply by 100 for percentage. No annotations provided, so description carries full burden; it adds useful behavioral context beyond a simple query description.

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 sentences efficiently convey purpose, output fields, and usage examples. No redundant information; every part earns its place.

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?

With no output schema, the description explains all return fields. It mentions the index size and provides query examples. Slight gaps (data freshness, pagination) but acceptable for a simple 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 covers all parameters with descriptions. The description mentions default sort 'apy' (already in schema) and provides example queries, but does not add new meaning to parameters. Baseline 3 is appropriate.

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 queries real-time stablecoin supply yield pools from 500+ protocols, with specific output fields. It naturally distinguishes from sibling tools (market overview, trend, payment stats) by focusing on DeFi yield data.

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 lists example use cases like 'best stablecoin yield' and 'compare lending rates', providing clear context. No exclusion or when-not-to-use, but siblings are different tools, so no confusion expected.

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