dual_stacking_opt_out

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

With no annotations, the description carries the full burden and does well: it discloses the unlocked-wallet precondition, the mainnet constraint, and the deferred timing of the opt-out with rewards continuing through the current cycle. It omits whether the action is reversible (can the wallet re-enroll later) and whether an on-chain transaction/fee is involved.

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?

Front-loaded with the action, then constraints, then a tip — a sensible order with little waste. The trailing 'Tip' line about earning_opportunities is mildly promotional but still routes the agent usefully.

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 zero-parameter mutation with no annotations and no output schema, the description supplies exactly what an agent needs to call it safely: wallet unlock requirement, network restriction, and the timing semantics of the effect.

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 tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate and it correctly avoids inventing parameters.

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?

States a specific verb and resource ('Opt out of Dual Stacking', 'Removes your wallet from the Dual Stacking protocol') and is immediately distinguishable from siblings like dual_stacking_enroll, dual_stacking_status, and dual_stacking_get_rewards.

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?

Gives clear operating context — mainnet-only, and the effect lands at the start of the next PoX cycle rather than immediately — plus a routing tip to earning_opportunities. It does not explicitly name 'dual_stacking_enroll' as the reverse operation or exclude other stacking exits, so it stops short of full alternative guidance.

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