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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the burden is lower, and the description still adds real value: the safe-by-default dryRun behavior, the requirement to opt in explicitly, that marketType=spot liquidates spot balances, and that the call executes with apikey identity directly. It does not state irreversibility or what credentials are covered when credentialId is omitted, which keeps it from a 5.

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 risk-critical information (write operation, requires confirmation, dryRun default) in a compact form. Slightly redundant: '(写操作' is repeated at the beginning and again in the trailing parenthetical, and the '(cost: free)' tag adds little for an agent.

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 destructive, zero-required-parameter tool this covers the essential safety contract and scoping. The main gap is that with no output schema, the description says nothing about what the dryRun preview returns versus the execution result, which an agent needs in order to report outcomes.

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, but the description adds meaning the schema lacks: dryRun defaults to true and must be explicitly false to execute, and marketType=spot has the specific effect of clearing spot balances. This is genuine semantic enrichment rather than restatement.

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 concrete verb and object: '一键全平' (close-all) under the 【持仓与执行】 category, plus scope modifiers (credential/symbol/marketType). An agent can tell this is an aggregate liquidation action rather than a single-order close, though it never explicitly names platform_close_position/platform_close_preview as the narrower alternatives.

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 explicit operating procedure: default dryRun=true is preview-only, real execution requires explicitly passing dryRun=false. Also explains scoping options. It stops short of stating when NOT to use it (e.g., for a single position use platform_close_position), so no exclusions are provided.

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