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

Annotations only declare readOnly/openWorld/non-destructive; the description adds substantial context beyond that: real-time broker connection latency ("may take a few seconds"), failure behavior on unsupported platforms, the platform support list, the fact that prices are per-account rather than global, and that the response includes traderwaiFeedPrice for comparison. No contradiction with the read-only annotation — the order rules are guidance for downstream tools, not claims that this tool mutates anything.

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?

Purpose is front-loaded in the first sentence and the feed-vs-broker distinction is laid out before the order rules, so structure is strong. It runs long for a two-parameter read tool, and the detailed LIMIT/STOP/stop-loss level rules arguably belong with execute_trade, but they are decision-critical to avoid misfired orders.

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 read-only quote tool with no output schema, the description covers what it returns (bid/ask plus traderwaiFeedPrice), latency, error cases, per-account variability, and platform coverage — everything an agent needs to call it and interpret the result correctly.

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% and already documents both symbol and brokerAccountId, so the description is not required to carry the load. It still adds meaning beyond the schema by emphasizing that prices differ per broker account and that the agent must resolve which account to quote when the user has several — a semantic constraint not visible in the schema.

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?

States a specific verb and resource ("Get the CURRENT price (bid and ask) of a symbol directly from the broker") and immediately disambiguates from the two sibling feed tools (get_ohlc / get_chart) by contrasting feed vs broker scope. An agent can pick it apart from get_ohlc/get_chart without opening either schema.

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?

Contains an explicit decision rule ("analyzing → get_ohlc / get_chart. Placing or proposing an order → get_quote first, every time") plus conditional alternatives for platforms without live prices ("it returns an error: then use get_ohlc as a reference") and for multi-account ambiguity ("if the user has several accounts and did not say which, ask or quote each one"). This goes well beyond what could be inferred.

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