fetch_intraday_data

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

With no annotations, the description discloses behavioral traits: 15-minute resolution, returns timestamp and close price, EST timezone, max 1000 bars (~10 trading days), and data source (Alpaca). It does not cover rate limits or authentication, but provides key behavioral context.

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 two paragraphs, front-loaded with the core action, and provides usage guidance without unnecessary words. It is efficient but could be slightly more concise.

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 the tool's simplicity (2 params, no output schema), the description covers input constraints, output format, and use cases. It lacks data delay or error handling info, but is adequately complete for a straightforward data fetch tool.

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% (description doesn't include parameter descriptions), but the schema itself describes parameters well. The description adds context about output (timestamp, close price) and the max bars limit, partially compensating for low coverage. However, it doesn't elaborate on parameter details beyond 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?

The description clearly states the tool fetches high-resolution 15-minute stock price data, specifying the verb 'fetch', the resource 'intraday stock price data', and distinguishes from siblings like get_price_history by emphasizing intraday granularity.

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 explicitly states when to use the tool (e.g., intraday price action, today's trading pattern) and provides example queries. However, it does not mention when not to use it or explicitly reference sibling alternatives.

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