Get live quotes

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

With no annotations, the description carries full burden. It discloses the data source (dxLink streamer) and return types, but does not explicitly state that the operation is read-only, nor does it discuss rate limits, error handling, or behavior with invalid symbols.

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 with colon-separated detail, effectively front-loading the main purpose. It is concise and to the point, though a slight restructuring could improve readability.

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 no output schema, the description should clarify the return shape. It lists data types but does not mention that the response is likely an array or map keyed by symbol. It covers symbol constraints and timeout, but omits error handling and response structure.

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 coverage is 100%, but the description adds substantial value by detailing the allowed symbol formats (equities, options, futures, etc.) and the data fields returned. For timeout_seconds, the schema already explains default and range, so the description does not need to repeat it.

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 action ('Get a live market data snapshot') and lists the specific data types (bid/ask, last trade, OHLC, Greeks). It also enumerates accepted symbol formats, distinguishing it from siblings like get_option_chain or get_market_metrics.

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 description implies usage for real-time snapshots but provides no explicit guidance on when to use this tool versus alternatives, nor does it state when not to use it. No mention of prerequisites or exclusions.

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