setDcp

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

No annotations are provided, so the description carries the full burden. It discloses institutional requirements, product types, time window range, need to activate DCP stream, and propagation delay. However, it does not mention whether the setting overwrites previous values, what happens if called multiple times, or any additional side effects beyond the cancellation behavior.

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 structured with bullet points and an agent hint, making it easy to scan. It front-loads the main purpose. However, the agent hint partially repeats the first sentence, and some information (like propagation delay) could be integrated without repeating the overall purpose. Minor redundancy.

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 no annotations and no output schema, the description covers prerequisites, products, time window range, activation steps, and propagation delay. It lacks details on response format or error handling, but for a simple configuration endpoint, it is sufficient 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 0%, so the description must compensate. It explicitly links 'product' to options, derivatives (futures), and spot products, and 'timeWindow' to a range of 3-300 seconds. While it doesn't give a detailed explanation of each parameter's purpose beyond the main description, it adds enough context for correct usage.

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 configures the time window for automatic order cancellation on WebSocket disconnection. It specifies the verb 'Configure' and the resource 'DCP time window', distinguishing it from sibling tools like getDcpInfo (read) and subscribeDcp (subscription). The agent hint reiterates the purpose.

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 provides clear context: institutional users only, must be enabled via account manager, and sequential steps (set then activate stream). It does not explicitly state when not to use or mention alternatives, but the sibling context and the explicit 'Agent hint' guide usage adequately.

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