Get Economic Calendar

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description adds that events are scheduled and date ranges are inclusive, but does not disclose additional behavioral traits such as rate limits or pagination. Given the annotation coverage, the description adds minimal extra value.

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 extremely concise: two sentences with no redundant words. The first sentence captures the core purpose and the second adds optional filter and default. Perfectly front-loaded and efficient.

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?

With an output schema present, the description does not need to explain return values. It covers the essential aspects: date range, country filter with default, and examples of event types. For a tool with 3 parameters (2 required) and an output schema, the description provides complete contextual guidance.

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% with detailed parameter descriptions. The tool description adds the default country behavior ('Defaults to US when omitted'), which is extra semantic information beyond the schema. This aids the agent in correctly invoking the tool.

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 identifies the tool as retrieving scheduled macro/economic events with a specific verb 'Get' and a resource clearly defined. It lists example events (CPI, FOMC, etc.) and specifies date range and optional country filter, making it easy to distinguish from sibling tools that handle different data types.

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: when to use it (to get economic events between dates) and includes a default behavior (countries default to US). However, it does not explicitly exclude alternatives or contrast with similar tools like get_earnings_calendar, leaving some ambiguity for edge cases.

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