subscribe_market_prices

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

With no annotations, the description carries the burden and it does disclose the core behavior—notifications on price changes. However, it omits subscription lifecycle details such as how long subscriptions last, what a successful subscribe returns, and whether it must be cancelled via unsubscribe_realtime.

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?

Two compact sentences, with the core action and event behavior front-loaded and no filler.

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?

Adequate for invoking the tool with well-described parameters and a clear purpose, but because there is no output schema the omission of return value and cancellation behavior leaves the full invocation lifecycle only partially described.

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 schema fully documents market_ids and callback_type. The description adds no parameter detail, matching the baseline of 3.

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?

Description names a specific verb ('Subscribe'), a specific resource ('market price changes'), and an event mechanism ('receives notifications'), which clearly distinguishes it from sibling tools like subscribe_orderbook_updates and get_current_price.

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?

Frames the intended scenario explicitly: 'useful for monitoring market movements and price action.' It provides clear context for when to choose this tool, though it does not spell out exclusions or alternatives.

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