setDcp

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

Beyond the annotations, the description discloses important behavioral consequences: automatic cancellation of all orders for the specified product after disconnection exceeds the window, institutional restrictions, required enablement, private WebSocket activation, and ~10 second propagation time. This adds substantial context beyond readOnlyHint/destructiveHint.

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 bullet list is tight and information-dense, with each line providing a non-obvious detail. The agent hint adds a concrete behavioral example without bloating the description. No filler or redundant restatement of schema fields.

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 two-parameter configuration endpoint with no output schema, the description covers prerequisites, allowed values, side effects, activation requirement, and propagation delay. An agent has everything needed to invoke it correctly and understand what will happen.

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?

Although schema description coverage is 0%, the description compensates by explaining the time window range (3-300 seconds) and supported product types (options, derivatives/futures, spot), which maps directly to the product enum and timeWindow constraints. It does not explicitly name the parameters, but the meaning is clear.

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 starts with a specific verb and resource: 'Configure the time window for automatic order cancellation when WebSocket connection drops.' It clearly distinguishes this setter from read/data siblings like getDcpInfo and from subscribeDcp by describing exactly what action it performs.

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 gives clear invocation context: institutional users only, must be enabled via account manager, time window range, activation of the DCP stream after setting, and propagation delay. It does not explicitly name alternatives or state when not to use it, though the prerequisites and follow-up sequence are clear.

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