t2000_unstake

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

No annotations provided; description adds context about returning SUI with yield and input format. Adequate for a simple unstake, but lacks details on permissions, balance checks, or side effects.

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?

Two concise sentences, front-loaded with main action and result, then usage. No unnecessary information.

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?

With one parameter and no output schema, description sufficiently covers purpose, input, and outcome. Could mention potential waits or fees, but not essential for such a focused tool.

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?

Only one parameter; schema description coverage is 100% and already explains 'amount' meaning. Description reinforces but adds little new semantic value beyond referencing 'all'.

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 action (unstake), resource (vSUI to SUI), and includes result (returns SUI with yield). Distinguishes from sibling t2000_stake (opposite).

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: amount in vSUI units or 'all' to unstake entire position. Implicitly when to use, but no explicit when not to or alternative tools mentioned.

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