subscribeRfqTrades

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

No annotations provided, so the description carries full burden. It only mentions authentication requirement. It does not disclose whether the subscription is one-time or continuous, how to manage the subscription, or what events are received. For a subscription tool, this is a significant gap.

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 very short (11 characters in Chinese), efficient, and front-loaded with key info. However, it sacrifices informativeness for brevity.

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 (a subscription tool with no output schema, no annotations, and many sibling tools), the description is incomplete. It lacks details on the event stream, subscription lifecycle, and differentiation from similar tools.

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?

Input schema has 2 parameters with 0% description coverage (schema has no descriptions). The description does not explain the meaning of messageCount or timeoutMs beyond their names and types. It fails to add value for parameter usage.

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 'Subscribe to RFQ trades (requires authentication)', which identifies the verb and resource but lacks specificity. It does not clarify whether these are public or private trades, nor does it distinguish from the similar sibling tool 'subscribeRfqPublicTrades'. The purpose is clear but vague.

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 vs alternatives. The only behavioral note is 'requires authentication', which is useful but insufficient for distinguishing from other subscribe tools like subscribeRfqPublicTrades, subscribeRfqQuotes, etc.

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