subscribeGreeks

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

The description discloses the authentication requirement but lacks details on subscription behavior (e.g., persistent vs one-time, data format, side effects). With no annotations, the description carries the full burden, which is insufficient.

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 sentence with no extraneous words. It is appropriately concise but omits critical information, balancing brevity and completeness poorly.

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?

The tool is simple but the description fails to explain the subscription mechanics, what 'Greeks' data includes, or how to use the output. Sibling tools suggest varied subscription behaviors, but this description provides no differentiation.

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 the two parameters (messageCount, timeoutMs) or their meaning, leaving the agent with no additional context beyond the schema definition.

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 uses a specific verb '订阅' (subscribe) and resource 'Greeks' to clearly indicate the tool's purpose. It distinguishes from sibling subscribe tools which target different data streams (e.g., subscribeAdlAlert, subscribeKline).

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 states a prerequisite (authentication required) but provides no guidance on when to use this tool versus alternatives (e.g., other subscribe tools) or when not to use it.

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