get_markets_calendar

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

Annotations already indicate read-only, non-destructive, idempotent. The description adds that all data is returned in a single response without pagination, which is useful behavioral detail. It also mentions supported plans but does not contradict annotations. Additional context would be rate limits, but not necessary given annotations.

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 concise and well-structured: a clear first sentence summarizing the tool, a note on pagination, supported plans, and a structured Args list. Every sentence adds value with 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 presence of annotations (readOnlyHint, etc.) and an output schema, the description adequately covers what the tool does, its parameters, and return content (trading days, holidays, half-day classifications). No gaps are apparent for a read-only data retrieval tool.

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?

Despite 0% schema coverage, the description includes an explicit Args section explaining each parameter: hol_div (division code meanings), date_from and date_to (date formats). This fully compensates for the lack of schema descriptions and adds essential semantics.

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 a market calendar with trading days and holidays. It distinguishes itself from sibling tools like get_equities_earnings_calendar and get_market_briefing by focusing on the overall market calendar rather than specific stocks or market overview.

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 explicit guidance on when to use this tool versus alternatives. The supported plans are mentioned, but there is no directive like 'use this for general market calendar, use get_equities_earnings_calendar for earnings dates.' Usage is implied from the purpose but not clarified.

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