watch_symbol

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

With no annotations provided, the description carries the full burden. It discloses auto-watch behavior, channel defaults, ohlcv timeframe suffix handling, and least-recently-used eviction when watch cap is exceeded. This is rich behavioral detail.

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?

Multi-sentence but every sentence earns its place. The structure moves from high-level purpose to specific channel behavior to eviction policy, with no redundancy.

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 accounts for the tool's complexity: optional pre-warm, auto-watch context, channel validation, ohlcv timeframes, and LRU eviction. An output schema exists, so return values need not be explained.

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%, so the description must compensate. It explains channels in depth (defaults, valid values, ohlcv suffix semantics) and implies symbol. Exchange is not explained, but the main tricky parameter (channels) is thoroughly covered.

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 tool's specific purpose: 'Pre-warm a live WebSocket subscription for a symbol'. It distinguishes itself from siblings by noting that most tools auto-watch on first use, so this is only needed occasionally.

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?

Explicitly states when to use ('only needed to warm a buffer ahead of time') and when not (most tools auto-watch). Does not name alternative tools, but the context is clear.

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