get_realtime_price

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

No annotations provided, so description carries burden. It discloses read operation and real-time IEX data, but doesn't disclose rate limits, latency, or authentication needs which are typical for price tools. Adequate for a simple read, but minimal.

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?

Description is concise and front-loaded: one sentence for purpose, then args. No wasted words.

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?

Covers purpose and parameters adequately. Output schema exists (not shown) so return values need not be explained. Could briefly clarify 'top-of-book' or real-time vs historical use, but overall sufficient.

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 0%, so description must add meaning. It defines ticker as 'Stock ticker symbol (e.g. AAPL.)' and after_hours as 'Include after-hours pricing data,' adding critical context beyond types.

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 gets 'the current real-time IEX top-of-book price for a stock,' specifying verb, resource, and scope. It distinguishes from sibling tools like get_stock_prices (historical) and get_intraday_prices (intraday).

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?

Usage is implied as real-time price retrieval, but no explicit guidance on when to use vs siblings (e.g., get_stock_prices for historical data, get_intraday_prices for intraday). No exclusions or alternatives mentioned.

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