unstake_stasis

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

With no annotations, the description carries full burden but only states it is an unwrap/sell operation. It fails to disclose key behavioral traits such as whether this action is destructive, irreversible, requires authentication, or what happens to the collateral mentioned in the 'unlock' parameter. The minimal description leaves significant ambiguity.

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?

The description is a single short sentence, which is concise and front-loaded. However, it is arguably too sparse for a mutation tool, slightly detracting from optimal structure. A 4 reflects good conciseness but room for more useful content.

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 the complexity of the action (unwrapping/selling staked tokens with boolean flags), no annotations, and no output schema, the description is incomplete. It omits crucial context like the order of operations when both unlock and sell are true, any fees, slippage, or return value, leaving the agent underinformed.

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% with clear parameter descriptions for 'unlock', 'sell_to_usdb', and 'shares'. The tool description adds no additional meaning beyond what the schema already provides, resulting in a baseline score of 3.

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 'Unwrap/sell staked STASIS' uses a specific verb ('Unwrap/sell') and resource ('staked STASIS'), clearly distinguishing it from sibling tools like 'stake_stasis' and general sell tools. The purpose is immediately understandable.

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?

No guidance on when to use this tool vs alternatives like 'sell_token' or 'stake_stasis'. The description does not specify context prerequisites or conditions under which this tool should be chosen.

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