get_upcoming_earnings

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

The annotations already establish read-only, idempotent, non-destructive, open-world behavior, so the description does not need to repeat safety traits. It adds the market-wide scoping and default look-ahead context, but does not disclose pagination, rate limits, or other operational behavior beyond what annotations already cover.

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 short and front-loaded: the core purpose appears in the first sentence, followed by compact parameter notes. Nothing is bloated, and the structure makes it easy for an agent to parse quickly.

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?

An output schema exists, so the description need not fully explain return values, though it briefly does. Both parameters are explained despite zero schema coverage. The main remaining gap is sibling differentiation from get_earnings_calendar and similar calendar tools.

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 carry parameter meaning. It does so for both parameters: days as the look-ahead window and limit as the maximum number of companies, with defaults noted. It does not add constraints such as valid ranges, but it compensates well for the bare schema.

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 states a specific verb and resource: get the market-wide earnings calendar for companies reporting in the next N days. The scope is clear, but it does not explicitly distinguish this tool from nearby siblings such as get_earnings_calendar or get_earnings_dates.

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?

It implies usage by describing the market-wide, look-ahead window, which fits an agent seeking upcoming earnings broadly. However, it gives no explicit when-to-use/when-not-to-use guidance or named alternatives, leaving sibling selection to inference.

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