dual_stacking_enroll

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

With no annotations, the description carries the full behavioral burden and does well: it discloses next-PoX-cycle activation, minimum sBTC holdings, wallet unlock requirements, reward-address behavior, and mainnet-only availability. It does not mention transaction fees or what happens if already enrolled, leaving minor gaps.

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 structure is front-loaded and readable, with prerequisites and behavioral constraints clearly separated. There is slight redundancy between the opening sentence and the next sentence, but no major bloat.

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 an enrollment mutation with no output schema, the description is complete enough: it covers timing, network restriction, balance and wallet prerequisites, and optional reward-address routing. An agent has the information needed to call it correctly.

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?

There is only one optional parameter, rewardAddress, and schema coverage is 100%, so the schema already documents it clearly. The description explains the same fallback behavior in prose but adds little beyond the schema baseline.

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 states a specific verb and resource: enroll a wallet in Dual Stacking to earn sBTC rewards. It is unambiguous and clearly distinct from adjacent tools such as dual_stacking_status or dual_stacking_opt_out, even without naming them.

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?

It gives clear prerequisites: an unlocked wallet, sufficient sBTC balance, and mainnet-only availability. It does not explicitly compare against alternatives like dual_stacking_status for checking eligibility or dual_stacking_opt_out for exiting, but the usage context is well defined.

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