withdraw_all

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

The description adds behavioral context beyond annotations, specifically the typical cost ('~90,000 energy + ~300 bandwidth'). It also confirms the destructive nature (all assets withdrawn). No contradictions with annotations (destructiveHint=true).

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?

The description is a single sentence followed by a cost note. Every word is essential, no redundancy. Front-loaded with the core action.

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?

The description lacks information about return values (e.g., transaction hash, status). While the action is simple, without an output schema, the description should briefly mention what to expect as a result. Otherwise, it is adequate.

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 parameter descriptions. The description adds no further meaning beyond what the schema provides (e.g., 'jToken symbol (e.g. 'jUSDT')' is already in the schema). 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 action ('Withdraw ALL supplied assets'), the resource ('JustLend market'), and the mechanism ('redeeming all jTokens'). It effectively distinguishes from sibling tools like 'withdraw' (partial) and 'supply'.

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?

The description implies use for full withdrawal only, but does not explicitly state when to use this tool versus the partial withdrawal sibling 'withdraw'. No when-not or alternatives are given, but the purpose is clear enough.

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