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

No annotations are provided, so the description carries the full burden. It discloses the return content at a high level ('expected dates'), but says nothing about whether dates are firm or tentative, the lookahead window, sorting, or the read-only nature of the call — all of which an agent would want for a calendar tool.

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?

A single front-loaded phrase with no wasted words and the core resource stated immediately. It is slightly too terse for the information gaps it leaves, but nothing is redundant.

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 tool with no annotations and no output schema, the description should explain the time window and what a release record contains. It omits the days default/max entirely and gives no sense of return shape, so an agent must open the schema and guess at behavior.

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 only 50%: the 'economy' parameter is documented in the schema ('Omit for all economies'), but the 'days' parameter has no description anywhere. The description does not reveal the default (14) or the 1-60 range, nor that it controls the lookahead horizon, leaving a key filter's meaning unstated.

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 names the resource precisely ('upcoming data releases that feed the nowcasts, with expected dates') and ties it to the nowcast family, making it distinguishable from siblings like get_nowcast or get_weekly_pulse. It lacks an explicit verb and doesn't state what it is not, but the resource and output content are unambiguous.

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?

There is no guidance on when to call this versus get_nowcast or get_weekly_pulse, nor any mention of prerequisites. 'Upcoming' implies a forward-looking time window, but nothing tells the agent when this calendar is the right choice over alternatives.

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