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

With no annotations at all, the description carries the full burden and does disclose the key destructive scope: every position the strategy opened is closed and unrelated positions are untouched. It omits whether the action is irreversible, whether proceeds are returned to the wallet, whether the strategy record is preserved or deleted, and what permissions are needed for a write operation of this weight.

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?

Two short sentences with the primary action front-loaded and the exception stated second; nothing is padded. It could be slightly sharper by naming the strategy identifier, but there is no wasted wording.

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?

There are no annotations and no output schema, so the description is the only behavioral documentation available, and it explains the position-closing scope adequately for that aspect. It is incomplete for the parameter side and says nothing about reversibility, result reporting, or authorization expectations for an irreversible-sounding liquidation.

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 description coverage is 0% for two required parameters (id, walletId), and the description adds nothing about either — not even that id identifies the strategy to stop or that walletId scopes it. For a destructive call, leaving both identifiers completely unexplained in both schema and description is a real gap.

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 gives a specific verb and resource ('Stop a strategy') plus the consequential side effect ('close every position it opened (cash out)'), which implicitly separates it from pause_strategy and resume_strategy in the sibling list. It never names those siblings, so an agent must infer the distinction rather than read it.

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 only implied by the word 'stop' versus the existing pause_strategy, resume_strategy, and update_strategy siblings; there is no explicit statement of when to choose stopping over pausing or what preconditions apply. The scoping rule about positions it did not open is a usage constraint of sorts, but it concerns behavior, not tool selection.

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