get_moolah_vaults

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

Annotations already declare readOnlyHint, idempotentHint, etc., so the description adds context about vault type (ERC4626) and yield mechanism but does not contradict annotations. Additional behavioral details (e.g., response shape, rate limits) are absent but not critical given annotations.

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, front-loaded with core functionality and data fields. No redundant text or padding.

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 simple list operation with optional parameters and no output schema, the description is largely complete. It explains the vault type and yield purpose. Minor omissions: no mention of pagination or response structure, but acceptable for this 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 descriptions cover 100% of parameters (network, depositToken). The tool description adds no extra detail beyond what the schema provides, such as default values or filter behavior. 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 lists all JustLend V2 (Moolah) vaults with specific data fields (APY, TVL, underlying token). It also distinguishes from sibling tools like 'get_moolah_vault' by indicating 'list all' and providing context about ERC4626 vaults.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., 'get_moolah_vault', 'get_moolah_vault_history'). The description implies it's for a broad overview, but no exclusions or when-not-to-use advice.

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