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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description adds real context beyond them: api_key auth requirement, the >= $10 USDC live-clone precondition and trading gate, and the important guarantee that pausing keeps open positions. That is exactly the state-effect detail an agent needs before invoking a destructive toggle.

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?

Dense but nearly every clause carries operational value, and the start/pause semantics are front-loaded. The opening 'Needs your api_key (register_agent, no key needed)' is slightly awkwardly phrased but still informative.

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?

With no output schema, the description still covers auth, preconditions (balance, trading gate), the paused-by-default clone lifecycle, and post-action state (positions retained), leaving no material gap for correct invocation.

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 100%, so all three parameters are already documented in the schema, and the description largely restates the enabled=true/false mapping. Baseline 3 is appropriate; it adds little syntax or format detail the schema does not already carry.

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 (start/pause) on a specific resource (one of YOUR clones) with the boolean mapping spelled out inline. It is clearly distinguishable from siblings like clone_bot, fund_clone_bot, and equip_bot_model, which create or configure clones rather than toggle trading.

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 a strong contextual trigger — 'A fresh clone starts PAUSED — this is how an agent enables it' — plus the paper vs live prerequisite. It stops short of naming an alternative tool (e.g., fund_clone_bot) for fixing the insufficient-balance case, so the routing is implied rather than explicit.

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