Unstake SOL (one-shot)

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

Discloses key behavioral traits: secret key handling (HTTPS, in-memory signing, no storage), cooldown period, and non-destructive nature. Adds value beyond annotations, which only provide openWorldHint=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?

Four short sentences with no redundancy. Front-loaded with purpose, immediately followed by key behavioral details and next steps. Every sentence earns its place.

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 the core operation, security, timing, and subsequent steps. Missing error conditions or multi-call behavior, but sufficient for a focused action tool given no output schema.

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?

Input schema has 100% description coverage, so baseline is 3. The overall description repeats the security aspect of secretKey but adds no new parameter meaning beyond the 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 it deactivates a stake account in a single call, with precise verb and resource. Distinguishes from sibling tools like create_unstake_transaction by emphasizing it's one-shot execution.

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 usage context: single call, cooldown ~1 epoch, and follow-up with check_withdraw_ready then withdraw. However, lacks explicit when-not or direct comparison to alternatives like create_unstake_transaction.

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