check_withdraw_readyCheck whether stake accounts are ready to withdraw. Returns per-account readiness with withdrawable epoch, estimated seconds remaining, and plain-English state description. Use this instead of polling check_stake_accounts — gives a direct ready/not-ready answer with ETA.
| Name | Required | Description | Default |
|---|---|---|---|
| walletAddress | Yes | Wallet address to check withdrawal readiness for |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds valuable context about return fields (withdrawable epoch, estimated seconds remaining, plain-English state description) without contradicting annotations.
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 concise sentences cover purpose, output details, and usage guidance. Every sentence earns its place with 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?
Despite lacking an output schema, the description adequately explains the return value composition and the intended use case for a simple one-parameter tool, making it complete for agent invocation.
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?
The schema already fully describes the sole parameter walletAddress with 100% description coverage, so the description adds no extra parameter information. Baseline of 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 states the specific action ('Check whether stake accounts are ready to withdraw') and distinguishes it from sibling tool check_stake_accounts by emphasizing a direct ready/not-ready answer with ETA.
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 recommends using this tool instead of polling check_stake_accounts, clearly stating the alternative and the advantage (direct answer with ETA).
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but there is some overlap between the 'stake' and 'create_stake_transaction' tools, as well as between 'unstake' and 'create_unstake_transaction', and 'withdraw' and 'withdraw_stake', which could cause confusion. However, descriptions clearly differentiate between automated and advanced manual use cases, mitigating ambiguity.
Tool names follow a consistent verb_noun pattern throughout, with clear and descriptive naming (e.g., check_balance, get_staking_summary, register_webhook). There are no deviations in style or convention, making the set highly predictable and readable.
With 26 tools, the count is borderline high for the staking domain, potentially overwhelming for agents. While many tools provide specialized functionality, some could be consolidated (e.g., multiple transaction-building tools), making the set feel slightly heavy but still within a reasonable scope.
The toolset comprehensively covers the staking lifecycle, including address checking, balance queries, staking, unstaking, withdrawing, monitoring, simulation, and verification. There are no obvious gaps, and tools provide clear guidance and alternatives, ensuring agents can handle all necessary operations without dead ends.