moolah_vault_redeem

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

Annotations already indicate destructiveHint=true, so the description adds the useful context 'No approval needed.' It does not contradict annotations. However, it could elaborate on the effect on vault state or the outcome of redemption.

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 concise sentences with zero wasted words. The first states the core purpose, the second provides a key usage hint. Fully earns its length.

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?

While the description is clear, it lacks details about the underlying assets or the post-redemption process (e.g., where assets go). Given no output schema, more completeness would be beneficial for a DeFi 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 all parameters. The description adds value by explaining the 'max' option for 'shares' and implying default for 'network'. This enhances the schema information.

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 action ('Redeem'), the resource ('vault shares'), and the result ('receive underlying assets'). It distinguishes from sibling tools like moolah_vault_deposit and moolah_vault_withdraw by focusing on the redemption of shares.

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 a specific usage tip ('Use shares='max' to redeem all shares') and states that no approval is needed. However, it does not explicitly compare with alternatives or mention when not to use this tool.

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