stocks_get_daily_open_close

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

There are no annotations, and the description only states the output type. It does not disclose behavior for invalid or non-trading dates, the effect of the 'adjusted' parameter, or any rate limits. However, it does specify the date format and the inclusion of after-hours prices, providing some 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 a single concise sentence, front-loads the key action and resource, and contains no filler. It is appropriately minimal.

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 lack of annotations and output schema, the description is minimal but covers the main data type and date format. However, it omits guidance on the adjusted parameter and edge-case behavior, making the tool somewhat underspecified for a complete understanding.

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?

The schema has 0% description coverage. The description adds context for the date parameter by specifying the YYYY-MM-DD format, and identifies the symbol as a stock, but does not explain the 'adjusted' boolean parameter, leaving one of three parameters undocumented.

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 retrieves OHLCV and after-hours prices for a stock on a given date, with the date format specified. It distinguishes from related sibling tools like previous_close and aggregate_bars by focusing on daily open/close with after-hours data.

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?

No guidance is provided on when to use this tool versus alternatives such as stocks_get_previous_close or stocks_get_aggregate_bars. The description lacks conditional usage instructions.

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