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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description's burden is lower. It adds behavioral context by stating the return includes scheduled date and indicator (not consensus), which is useful but does not disclose data freshness or scope limitations beyond 'US release calendar.'

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 at two sentences, front-loading the key events list and purpose. Every clause adds value, though the structure could be slightly improved by separating the return type more explicitly from the usage guidance.

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?

For a simple tool with one optional parameter and an output schema, the description covers its core purpose, input range, and what it returns (scheduled date and indicator). It explicitly notes it does not return consensus, which is helpful. Missing a brief note on data source limitations (US-only) is a minor gap.

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 coverage is 100%, and the single parameter 'days' is well-described in the schema with default and purpose. The description adds no additional semantic information about the parameter, meeting the baseline but not exceeding it.

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 scheduled macro events (CPI, PCE, NFP, GDP, Retail Sales, FOMC) from the official US release calendar. It provides specific examples and distinguishes from sibling tools like get_macro_rates by focusing on event dates rather than rate data.

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 advises calling for 'upcoming economic catalysts,' giving clear context for when to use the tool. However, it does not mention when not to use it or explicitly compare to siblings like get_macro_rates, leaving some situational guidance implicit.

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