get_earnings_calendar

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states the purpose and does not disclose return format, date range semantics, pagination, or read-only behavior. This is a minimal disclosure beyond the bare function.

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 a single, front-loaded sentence with no filler. It is concise and immediately communicates the tool's purpose.

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?

The tool is simple with only two optional date parameters and no output schema. The description is adequate for basic selection and invocation, but lacks details on the response format or how 'upcoming' interacts with the date range, leaving some ambiguity.

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% for the two parameters ('from' and 'to' dates). The description adds no additional meaning about how these dates affect the calendar, but the schema already documents them, 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?

The description 'Get upcoming earnings announcements calendar' clearly states the tool's function with a specific verb ('Get') and resource ('earning announcements calendar'). It is unambiguous but does not explicitly differentiate from sibling calendar tools like get_economic_calendar, so it falls short of a 5.

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 implies usage for retrieving upcoming earnings announcements, but provides no explicit guidance on when to prefer this tool over alternatives such as get_economic_calendar or get_analyst_ratings. There are no exclusions or alternative names mentioned.

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