write.account.withdraw

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

Beyond annotations, description discloses revert conditions, unsupported max_uint256, and auto-detection of account version. Does not mention rate limits or side effects beyond reverts, but idempotentHint already indicates safety.

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?

Four sentences, all essential, front-loaded with purpose, no redundancy.

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 complexity and existence of output schema, description adequately covers behavioral constraints, prerequisites, and parameter guidance, making the tool fully usable.

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 covers all 7 parameters with descriptions (100% coverage). Description adds minor value by advising exact amounts from read.account.info, but does not significantly enhance parameter understanding 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 the tool builds an unsigned transaction to withdraw assets from an Arcadia account to the owner's wallet, with a specific verb and resource, distinguishing it from other write.account.* siblings.

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 clear context: only owner can withdraw, reverts if undercollateralized, no max_uint256, and recommends using read.account.info for amounts. Does not explicitly list alternatives but purpose is distinct enough.

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