ws_subscribe_price

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

With no annotations, the description carries the full burden of behavioral disclosure. It fails to mention that the subscription is stateful, may need to be managed or unsubscribed, or that updates are likely received separately via ws_get_updates. The persistent nature and side effects of subscribing are not disclosed.

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 of ten words. It is concise, contains no fluff, and every word contributes to the core purpose.

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, critical context is missing: how to receive updates, whether a subscription ID is returned, how to unsubscribe, and the expected ongoing behavior. The absence of an output schema and sibling-tool references leaves the agent underinformed about the full workflow.

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 100%, so the baseline is 3. The description adds no new meaning beyond what the schema already provides; it merely restates 'trading pair' (symbol) and does not elaborate on the exchange parameter or 'aggregate' semantics.

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 uses a specific verb 'Subscribe' and clearly identifies the resource as 'real-time price updates for a trading pair'. It distinguishes this tool from sibling subscriptions like ws_subscribe_wallet, ws_subscribe_blocks, and ws_subscribe_pool, which target different data streams.

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?

The phrase 'real-time price updates' implies the tool is for streaming data, but it does not explicitly state when to use it vs. alternatives, nor does it mention exclusions or related subscription-management tools like ws_get_updates or ws_unsubscribe. Usage guidance is only implied, not explicit.

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