subscribeGreeks

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

The annotations already mark the tool read-only and open-world, which lowers the burden. The description adds that this is a push-style subscription and that authentication is required. Still, it does not disclose whether this is a WebSocket stream, how long it stays active, or how the subscription is terminated.

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, front-loaded sentence with no filler, so it is very concise. It is slightly too terse for a streaming subscription with two parameters, but there is no wasted text.

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?

For a subscription tool with no output schema, an agent needs to know what a Greeks push returns, how timeoutMs and messageCount affect delivery, and what scope the subscription covers. The description only provides the resource and an auth prerequisite, leaving significant operational gaps.

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?

The schema has 0% description coverage and the tool description does not mention timeoutMs or messageCount at all. The parameter names and defaults give some clue, but the description fails to explain how these two parameters interact or what messageCount actually controls.

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 states a concrete action ('subscribe') and a distinct resource ('Greeks push'), which separates it from siblings like subscribeTickers or subscribeSystemStatus. It is not a tautology, but it does not explain what the Greeks payloads actually contain.

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?

Usage is only implied: the tool exists to receive Greeks push updates, and the parenthetical 'requires authentication' adds a prerequisite. However, there is no guidance about when to choose this over alternatives such as getCoinGreeks or other subscribe* tools.

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