subscribeSpreadOrder

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

The description discloses that authentication is required ('需要鉴权'), which is a critical behavioral trait. However, it does not mention whether the subscription is persistent, how to stop it, rate limits, or event frequency. With no annotations, this is a minimal but incomplete disclosure.

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 a single, concise sentence that is front-loaded with the action and resource. No unnecessary words or 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 the lack of output schema and the subscription nature, the description fails to explain how the tool works (e.g., persistent vs. poll), what events are returned, or how to use parameters. Sibling tools suggest subscription behavior, but the description offers no context for a complete understanding.

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 0%, and the description does not mention any parameters (messageCount, timeoutMs). It provides no additional meaning beyond the input schema, leaving the agent to infer parameter usage without context.

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 subscribes to Spread order changes, specifying the exact resource ('Spread order') and action ('subscribe'). It distinguishes from sibling subscribe tools like subscribeOrder and subscribeSpreadOrderbook by specifying 'Spread order' rather than generic orders or other spread data.

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?

No guidance on when to use this tool versus alternatives. The description only states what it does, with no mention of scenarios where this is appropriate or exclusion of other subscribe tools.

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