Toss Get KR Market Calendar

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

The description implies a read-only operation ('Get'), which aligns with no destructive behavior. However, since no annotations are provided, the description does not disclose what happens if an invalid date is provided or if the date is omitted (whether it returns current day or all dates).

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 sentence that states the purpose and notes the parameter. Every word is relevant, and there is no redundancy.

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 has only one optional parameter and no output schema, the description is minimally complete. It covers the basic action and parameter format but lacks details on return values, error handling, or behavior for omitted dates.

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 description adds minimal value beyond the schema: it states 'date is optional YYYY-MM-DD'. The schema already defines the pattern; the description does not explain what the parameter controls (e.g., specific date's calendar vs full calendar) or provide examples.

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 Korean market calendar and session hours. It distinguishes from the sibling 'toss_get_us_market_calendar' by specifying 'Korean'. However, it does not detail what the calendar includes (e.g., holidays, trading days).

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 usage guidelines are provided. There is no mention of when to use this tool versus alternatives like 'toss_get_us_market_calendar' or how to handle missing dates. The distinction is only implicit in the name.

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