subscribeWallet

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

With no annotations, the description carries the full burden. It does not explain behavioral aspects such as connection management, how to stop receiving updates, or the meaning of the parameters (messageCount, timeoutMs). The term 'real-time' is vague.

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, very concise. However, it omits necessary context for a subscription tool among many siblings, so its brevity sacrifices completeness.

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 it is one of many similar subscribe tools with 2 undocumented parameters and no output schema, the description lacks completeness. It does not describe expected inputs, outputs, or how the subscription lifecycle works.

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 input schema has 0% description coverage and the tool description does not explain the parameters at all. messageCount and timeoutMs are left to the user's interpretation, adding zero meaning beyond their names.

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 clearly states the verb 'subscribe' and the resource 'wallet updates' for the 'Unified Trading Account (UTA)'. It distinguishes this tool from numerous other subscribe tools focused on different resources (orderbook, tickers, etc.).

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 provided on when to use this tool versus the many other subscribe tools (e.g., subscribeOrderbook, subscribeTickers). There is no mention of prerequisites, alternatives, or exclusion criteria.

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