subscribeAdlAlert

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

With no annotations, the description must disclose behavior. It does not explain whether subscription is persistent, if it can be cancelled, authentication needs, or what triggers the push. The description only states the action without any behavioral context.

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, but it may be too brief for a subscription tool. It is front-loaded but lacks sufficient detail, earning a middle score.

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 complexity of a subscription tool with three parameters and no output schema, the description is incomplete. It does not explain what ADL alerts are, subscription lifecycle, or how to interact with the subscription (e.g., unsubscribing). It provides minimal context for 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%, and the description adds no meaning beyond parameter names. The parameters (coin, messageCount, timeoutMs) are self-explanatory, but the description does not clarify their roles or constraints.

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 '订阅 ADL 预警推送' clearly indicates the tool subscribes to ADL (Auto-Deleveraging) alert push notifications. It distinguishes from other subscribe tools for different data streams, and from getAdlAlert which likely queries alerts. However, it could be more explicit about the nature of ADL alerts.

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 like subscribeKline or getAdlAlert. There is no mention of prerequisites, context, 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.