get_market_calendar_us

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

No annotations are provided, and the description does not disclose any behavioral details such as return format, timezone, whether holidays are included, or the range of dates covered. It merely restates the tool's purpose, leaving the agent without critical information about what the tool actually returns or how it behaves.

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, front-loaded sentence with no redundant words. It efficiently conveys the tool's purpose, earning full points for conciseness and structure.

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?

The tool is simple with one optional parameter, and the schema covers that parameter. However, the description does not explain what the returned calendar contains (e.g., holidays, trading sessions) or the format of the response. With no output schema, this missing semantic context makes the description merely minimum viable.

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 provides full coverage (100%) for the single 'date' parameter with a clear description ('Optional date (YYYY-MM-DD)'). The description adds no additional parameter semantics, so the baseline score of 3 is appropriate.

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 the US market operating calendar, using a specific verb ('Get') and resource ('US market operating calendar'). It distinguishes from the sibling get_market_calendar_kr by explicitly indicating US market, and the Korean phrase reinforces overseas market context.

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 provides clear context that this is for the US market, making its usage obvious. However, it does not explicitly mention alternatives or exclusions, such as directing users to get_market_calendar_kr for the Korean market. The sibling presence implies the distinction, but it is not stated.

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