update_hl_copy_trade_settings

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

Adds meaningful behavior beyond annotations: it reads current config first, preserves omitted fields, and does not delete or pause/resume. The SDK repair note is valuable context for a mutation tool, though it does not cover authorization needs or whether changes affect live positions.

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?

Front-loaded with the core action, then exclusions, merge behavior, and repair guidance in four tight sentences. Every sentence adds operational value without repetition.

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?

Given 12 parameters, mutation annotations, and no output schema, the description covers the most important operational behavior, exclusions, and legacy repair case. It leaves minor gaps around auth/accountRef expectations and the exact result shape, but remains sufficiently complete 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 coverage is 100%, so the baseline is 3. The description earns extra credit by explaining merge semantics for omitted fields and by naming copyMode, fixedAmountCostPerOrder, and oppositeCopy as the explicit repair trio for invalid legacy configs.

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: "Change settings of an existing HL perp copy trade." It also distinguishes this from delete/pause/resume operations by explicitly saying it never performs those actions, so an agent can separate it from key siblings.

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?

Clearly indicates this is a settings-change operation and explicitly excludes delete and pause/resume use cases. It also gives a concrete repair scenario, though it does not explicitly route pause/resume/delete callers to the named sibling tools.

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