atstake_legion_redeem_vault

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

With no annotations, the description carries the full burden and delivers: it explains the state change (shares redeem at 1 sat into the credits pot, or are recorded as worthless if the side lost), that it pays the caller nothing, that it is permissionless and once-only, and the exact timing condition.

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 key action and scope are front-loaded in sentence one, and the wagering of preconditions follows logically. The lost-side sentence ('which is still the call that has to happen before anyone learns their credit pays zero') is a touch verbose for the value it adds.

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?

For a no-annotation, no-output-schema mutation tool, the description covers effect, timing, cost, wallet requirement, and both win/lose outcomes. Nothing an agent needs to decide whether and how to call it is missing.

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 the single enum parameter already documents all four values, so the schema does the explanatory work. The description contributes no additional detail about how 'side' selects the vault beyond the name-level notion of 'the legion's side'.

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 first sentence gives a concrete verb+resource: 'Turn a winning legion's leftover shares into sBTC.' The scoping ('legion's leftover shares', vault conversion) distinguishes it from per-user tools like atstake_redeem, though no sibling is named explicitly.

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?

Preconditions are spelled out: permissionless, once-only, callable only after the market resolves and all live proposals have settled, requires an unlocked wallet. It stops short of explicitly naming the alternative tool for individual (non-legion) redemption, so the agent must infer the boundary.

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