yield_hunter_stop

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

With no annotations, the description carries the load, and it does disclose real behavior: a background process monitoring and depositing sBTC, and that existing Zest positions are left untouched. It does not say whether the stop is reversible without yield_hunter_start, what happens to an in-flight deposit, or whether auth/unlock is required.

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?

Three short sentences, front-loaded with the action, followed by a state-safety clarification. The closing tip is slightly tangential but earns its place by redirecting the agent after stopping.

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-param, no-output-schema control tool, the essentials are covered: what is stopped, what is preserved, and where to go next. The main omissions are restart guidance and whether the halt takes effect immediately for pending deposits.

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 there is nothing for the description to disambiguate; the baseline for a no-arg tool applies.

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 ('Stop autonomous yield hunting') and clarifies it in the second sentence as the background process that monitors and deposits sBTC. This clearly separates it from yield_hunter_start/status/configure by implication, though it never names those siblings 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?

Usage is implied: you call it to halt the automated yield hunting. The 'Tip' points to earning_opportunities, but that is a post-stop next step rather than guidance on when to stop versus, say, reconfigure via yield_hunter_configure. No exclusions or prerequisites are stated.

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