get_market_calendar

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

With no annotations, the description carries the disclosure burden. It states the resource and the optional date, but it does not clarify the meaning of 'around' (exact date vs range), timezone handling, or behavior on holidays/non-trading days. This is adequate for a simple read-only lookup but leaves ambiguity.

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 purpose is stated in the first sentence, and parameter guidance is formatted as a compact labeled list. The Korean translation is the only redundancy but is brief and does not distract.

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?

For a two-parameter read-only tool with an output schema, the description covers both parameters and the market choices. The main remaining gaps are the exact date-range semantics and timezone, but these are unlikely to prevent correct invocation.

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%, but the description fully compensates: market is constrained to 'KR' or 'US', and date is documented as optional YYYY-MM-DD with clear omission behavior. This adds meaning beyond the bare schema and removes ambiguity about accepted values.

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 names a specific verb and resource: 'Get market session times (pre/regular/after-market)'. It also narrows scope by market ('KR' or 'US') and date, making it clearly distinct from sibling price/candle/orderbook tools.

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 gives clear invocation context: pass a market and optionally a date, omit the date for today. It does not name alternatives or explicit when-not-to-use, but no sibling tool overlaps with market session times, so this is not a significant gap.

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