subscribeSpreadTickers

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

With readOnlyHint=true and openWorldHint=true, the safety profile is already declared; the description adds that this is a subscription returning market snapshots. It does not disclose termination semantics such as how timeoutMs and messageCount control the snapshot stream, though that is partly visible in the schema.

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, direct sentence with no filler and the key resource is front-loaded. It loses one point because it is arguably too terse to be 'appropriately sized', but there is no wasted wording.

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?

There is no output schema, yet the description does not explain return format, stream lifetime, or the effect of the two optional parameters. Given the large sibling family of subscribeSpread* and getSpread* tools, the description is too sparse to fully orient an agent.

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%, so the description needed to explain timeoutMs and messageCount. It does not mention either parameter or their effect, leaving the agent without any parameter semantics beyond the raw schema.

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 '订阅 Spread 行情快照' states a specific action (subscribe) and resource (Spread market snapshots), which is enough to identify the topic. However, it does not explicitly contrast it with sibling tools like subscribeTickers or getSpreadTickers, so some differentiation is left to the name and context.

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?

There is no guidance on when to choose this subscription over the many sibling subscribe/get Spread tools. The agent must infer from the name that this is the streaming alternative to getSpreadTickers, and nothing in the description states the intended use case or exclusions.

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