withdraw

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

Adds value beyond annotations by warning about potential failure due to collateral and quoting typical energy/bandwidth costs. Aligns with destructiveHint=true. No contradiction.

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?

Three sentences, front-loaded with the core action, then important caveats and cost. No unnecessary 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?

Covers action, failure condition, and cost. No output schema, so return values are not expected. May benefit from mentioning that it's specific to JustLend protocol, but that's implicit.

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%, so baseline is 3. The description adds clarification that the amount is in underlying units, which is useful beyond the schema's description. Market and network are already clear from 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?

Clearly states the action (withdraw/redeem), resource (supplied assets from JustLend market), and distinguishes from siblings like borrow, supply, and withdraw_all by specifying the context of redeeming supplied assets.

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 key usage context: may fail if assets are used as collateral for borrows, and typical cost. However, does not explicitly state when not to use or mention alternatives, though the warning about collateral implies a prerequisite.

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