Market holidays for a year

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

No annotations are provided, so the description must suffice. It indicates a read operation ('List') but does not explicitly state it is non-destructive or clarify edge cases (e.g., weekends, future years). Basic transparency for a simple list tool.

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?

One sentence of 12 words, front-loading the purpose. No redundant information. Excellent conciseness.

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?

Covers the main purpose and output format. Lacks explicit mention of return type (array) and whether holidays include names, but for a simple list tool with well-documented 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?

Schema description coverage is 100%, so the schema already documents both parameters. The description adds minimal value beyond restating 'given calendar year', which matches the 'year' parameter. Baseline 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 verb 'List' and the resource 'exchange holidays' with output format 'YYYY-MM-DD' and context 'for a given calendar year'. It distinguishes from siblings like 'is_trading_day' which checks individual dates.

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 implies use when needing a list of holidays for a year, but does not explicitly state when to use it over alternatives (e.g., 'is_trading_day') or provide exclusions.

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