getEarningsCalendar

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. The description adds the 'upcoming and past' temporal scope, which is useful context, but says nothing about pagination, result caps, or data freshness. Adequate but not rich given the low bar set by annotations.

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 first sentence opens with promotional filler ('Stay informed on...') rather than the operation itself, and the second restates the returned fields. It is short, but the lead-in does not earn its place.

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 read-only calendar endpoint with no output schema, full schema coverage, and annotations carrying the safety profile, the description is complete enough for correct invocation. Missing only sibling routing and pagination 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 description coverage is 100%, with 'to', 'from_date', and 'includeReportTimes' each documented in the schema. The description mentions date and EPS fields but adds no syntax or format detail beyond what the schema already provides, so the baseline of 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 specific resource (earnings calendar) with a clear scope of upcoming and past announcements and lists the data returned (dates, estimated EPS, actual EPS). It is understandable without opening the schema, though it does not distinguish itself from siblings like getEarningsReports, getEarningsTranscriptList, or getEarningsSurprisesBulk.

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 gives no when-to-use guidance and names no alternatives, despite several sibling tools (getEarningsReports, getEarningsTranscriptList, getEarningsSurprisesBulk, getDividendsCalendar, getEconomicCalendar) that an agent must choose between. Only implied usage as a calendar lookup.

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