Get Intraday Price Bars

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

Annotations already set readOnlyHint=true. Description adds the extended-hours behavior constraint (only with resolution 1) and lists returned fields, but doesn't discuss other behavioral aspects like authentication, rate limits, or data adjustment. Adequate given annotation coverage.

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?

Three sentences, each adding value: first states action and options, second gives use case, third explains extended-hours nuance. No wasted words, front-loaded with essential information.

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, parameters (via schema), and a key behavioral nuance. Output schema exists and can detail return format. A mention of timezone or data source could improve completeness, but not strictly necessary.

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 parameters are already well-documented. The description reiterates the extended-hours condition but adds minimal extra meaning beyond summarizing the schema. Baseline 3 is appropriate.

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 specifies it retrieves intraday OHLCV candles at discrete resolutions (1,5,15,30,60 min). It distinguishes from sibling tools like get_historical_prices (likely daily) and get_quote (current) by explicitly mentioning 'intraday' and the resolution options.

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?

States use for 'intraday price action analysis, volume patterns, and short-term technical analysis,' providing clear context. Does not explicitly exclude other uses or name alternatives, but the context is sufficient given many sibling tools.

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