prepare_native_stake_withdraw

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

Adds value beyond annotations by describing partial vs full withdrawal effects, simulation gate, and nonce requirement. No contradiction with annotations (destructiveHint=true for 'max', idempotentHint for building tx).

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, front-loaded with purpose. All sentences add value, though could be slightly more concise. No filler.

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 all essential behavioral aspects: purpose, prerequisites, effects on account, nonce requirement, and safety (simulation gate). Missing explicit mention of output format, but no output schema exists so not required.

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%, and description adds extra context for amountSol (example, 'max' behavior, partial vs full). Reinforces parameter descriptions without redundancy.

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?

Description clearly states it builds an unsigned native-stake withdraw tx from an inactive stake account, explaining 'max' closes the account and partial withdraw leaves it open. Distinguishes from siblings like deactivate and delegate.

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?

Explicitly states the stake must be inactive and a durable nonce is required, providing clear context for when to use. Mentions similar Ledger treatment as a sibling, but does not explicitly list alternatives or when-not scenarios.

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