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

Annotations indicate mutation (readOnlyHint=false) but the description adds that the strategy is no longer dispatched, clarifying the behavioral effect. However, it does not mention reversibility or permissions, though destructiveHint=false suggests non-destructive state change.

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 description is a single sentence of 16 words, front-loaded with the action verb 'Stop'. Every word is necessary and no redundant information is present.

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 simple cancellation tool with an output schema present (though not shown), the description covers the primary effect and purpose. It lacks guidance on usage vs. pause, but is otherwise sufficient for an agent to invoke the tool 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?

The input schema has two required parameters (strategy_id, wallet_address) with no descriptions (0% coverage). The description does not explain their purpose or why wallet_address is needed, leaving the agent without added semantic meaning beyond the schema.

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 clearly states the tool stops a strategy by setting its status to stopped and preventing further dispatch. It uses a specific verb ('Stop') and resource ('strategy'), differentiating it from sibling tools like strategy_pause which likely implies temporariness.

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?

The description implies this is a permanent stop ('will not be dispatched again'), contrasting with strategy_pause which may be temporary. However, it does not explicitly state when to use this over alternatives, leaving room for inference.

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