get_intraday

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

Annotations (readOnlyHint, idempotentHint, openWorldHint) already indicate a safe, read-only operation. The description does not contradict annotations but adds no further behavioral details (e.g., rate limits, pagination), so it meets baseline expectations.

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 very concise: a single sentence for purpose, XML tags for strategy and example, and a brief Args section. It is front-loaded with the key action and contains no fluff.

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 parameters, no nested objects, with output schema), the description covers the main need: getting intraday data for a symbol on a date. It doesn't explain timezone or range limits, but with existing annotations and output schema, it is reasonably complete.

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?

With 0% schema description coverage, the description adds 'Date YYYY-MM-DD (default: today)' and explicitly lists parameters, providing format and default information beyond the schema titles. This compensates for the lack of schema descriptions.

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 'Get intraday time-share data for a symbol', using a specific verb and resource. It distinguishes from siblings like get_quote (snapshot) and get_candlesticks (candlestick data) by focusing on intraday tick 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?

The description includes '<strategy>Directly invoke for intraday price ticks.</strategy>', implying when to use. It provides an example but does not explicitly mention when not to use or alternatives, though the context of sibling tools implies them.

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