subscribePublicTrade

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

The description adds little beyond the tool name and annotations. It does not disclose that this is a subscription that may run until timeoutMs, that it returns a specific number of messages via messageCount, or how the stream behaves. Annotations indicate read-only and open-world, but the description itself provides minimal 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 short sentence with no filler or redundant content. It is front-loaded and wastes no words, which is appropriate for such a simple tool name.

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 description is far too sparse for a subscription tool with no output schema and four undocumented parameters. An agent cannot determine how long the subscription lasts, how many messages it will receive, what data is returned, or how to stop it. It also fails to distinguish itself from the many related trading-data siblings.

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 explain the meaning or purpose of symbol, category, timeoutMs, or messageCount. The agent is left to infer parameter semantics entirely from names and schema defaults, with no narrative support.

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 specific action ('subscribe') and a resource ('real-time trade data'), matching the tool name. It is reasonably clear what the tool does, though it does not explicitly call out 'public trades' or differentiate from the similar sibling subscribeSpreadPublicTrade.

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 is given about when to use this subscription versus alternatives such as getRecentPublicTrades, getPublicTrades, or subscribeTickers. The description does not explain whether this is a one-shot fetch or a continuous stream, nor how it relates to sibling tools.

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