economic_calendar

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

With no annotations, the description carries the full burden and does it well: timezone (ET), weekday-only cadence, weekend roll behavior, the critical warning that events=null means unserved/unverified rather than quiet, and the forexfactory provenance tagging. These are exactly the non-obvious traits an agent would otherwise get wrong.

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?

Front-loaded one-line purpose, then the field/return contract, then the null caveat, then a compact Args block. Every sentence adds operational information; nothing is filler.

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?

No output schema exists, and the description compensates by naming the returned fields (impact, actual, consensus, previous) and explaining the null-day edge case. Combined with full parameter documentation, an agent has everything needed to call and interpret it.

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 0%, so the description must compensate and does: date format YYYY-MM-DD plus default and roll semantics, days as a weekday count, impact's accepted values 'all'/'high', and forexfactory as a boolean with scope restrictions and side effects (source tagging).

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 specific verb and resource with tight scope: 'Get scheduled US economic releases (CPI, NFP, FOMC, GDP, PCE, ISM...) per weekday, in ET.' The examples disambiguate it from the earnings-focused sibling earnings_calendar without naming it directly, though no sibling is explicitly contrasted.

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?

Gives clear usage context: defaults, weekend rolling to Monday, impact filtering, and the precise condition under which forexfactory should be used (gap-filling, current Sun-Sat week only). It does not state when NOT to use this tool or point to an alternative for non-US or non-scheduled events.

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