get_calendar

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully reveals that unbounded requests return an extremely large multi-year response, but it leaves 'formats' vague and does not specify what the calendar entries represent beyond what the schema's date_type parameter already describes.

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?

Two focused sentences: the main action is stated first, and the critical warning follows immediately. There is no redundant or filler content.

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?

An output schema exists and all parameters are documented in the schema, so the description need not repeat return details. The warning covers the main invocation hazard. Still, a brief mention of what the calendar contains (e.g., trading holidays, non-trading days) would make it fully self-contained.

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 covers all parameters, so the baseline is 3. The description adds value by specifying the expected YYYY-MM-DD format and by warning that both bounds should always be supplied even though they are not required by the schema. It adds no new semantics for date_type, but the schema already documents that enum.

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 states a specific verb and resource ('Retrieves and formats market calendar') and limits scope to a date range. It does not explicitly differentiate from sibling tools, but the 'market calendar' resource is distinct enough among the listed siblings.

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 warning clearly instructs the caller to always provide start and end dates, explaining the consequence of omission. It does not mention alternatives or when-not-to-use, but there is no obvious sibling for calendar retrieval.

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