get_economic_calendar

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

With no annotations, the description carries the full burden. It usefully discloses the nature of the return content (an official announcement schedule rather than indicator values), but says nothing about ordering, timezone/date semantics, data source latency, or pagination behavior beyond the limit parameter.

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 tight sentences with the core purpose front-loaded and the filtering capability trailing. No filler, though the second sentence is fairly generic.

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?

A simple read-only list tool with zero required params, so little is strictly needed. However, with no output schema and no annotations, the description could say more about the shape of returned events (fields, ordering) to be fully self-sufficient.

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 limit, range, impact and country with enum values. The description adds no syntax or format detail beyond restating the country and impact filters, so the baseline 3 applies.

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?

States a clear verb+resource: returns the official announcement calendar of macro data, explicitly listing the categories (central bank rate decisions, CPI, GDP, employment). This distinguishes it from value-returning siblings like get_macro_indicators or get_inflation_data, though it never names an alternative directly.

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?

Usage is only implied — an agent infers you call this to see upcoming macro events. The sentence about filtering by country and impact level is parameter description, not guidance. No when-to-use, when-not, or alternative-tool routing is given.

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