get_aave_reserve

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

Describes the return values (full reserve config, rates, TVL, etc.) and includes a rate conversion formula. No annotations are provided, so the description carries the full burden, which it handles well. 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 front-loaded with usage guidance, then return content, then a conversion tip. Every sentence is informative and concise, 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?

Given the tool's simplicity (2 parameters, no output schema), the description adequately explains what data is returned and provides a conversion hint. It lacks explicit mention of error cases or performance, but is sufficient for a detail retrieval 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 coverage is 100% with descriptions for each parameter, but the description adds useful context such as case-insensitivity for symbol and examples tying parameters to use cases. This adds marginal value beyond schema.

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 'Use this when the user asks about a specific AAVE asset in detail' with concrete examples (e.g., 'Tell me everything about USDC on Ethereum AAVE'), identifying the specific verb (get) and resource (reserve) and distinguishing it from sibling tools like get_aave_reserves.

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 specifies when to use with examples and context ('e.g. Tell me everything about USDC...'), but does not explicitly state when not to use or provide alternative tools for comparison, though the differentiation from siblings is implicit.

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