veroq_defi_protocol

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

Despite no annotations, description discloses key behavioral traits: it returns TVL, 1d/7d/30d change percentages, category, and deployed chains. Also mentions cost of 2 credits and provides an example. 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: purpose, usage guidelines, return fields, cost, and example. Every sentence serves a clear purpose with no unnecessary information.

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 simple tool with single parameter and no output schema, description covers all necessary aspects: what it does, when to use, what it returns, cost, and example. Sufficient for correct invocation.

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% with a clear description of 'protocol' parameter. Description adds value by including an example usage ('{"protocol": "uniswap"}') which reinforces correct invocation.

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?

Description explicitly states the verb 'Get' and resource 'detailed DeFi protocol data including TVL, chain deployment, and performance changes'. It clearly distinguishes from sibling 'veroq_defi' which provides a full market overview without arguments.

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 'WHEN TO USE' section: 'For a deep dive into a single DeFi protocol. Use veroq_defi (no args) for the full DeFi market overview.' This gives clear context and alternative.

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