earnings_calendar

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

With no annotations, the description provides some behavioral context: it is sourced live from Nasdaq's public calendar, and focuses on US equities. However, it omits details like rate limits, authentication needs, data freshness guarantees, or error scenarios.

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 repetitive (first sentence duplicated) and could be more streamlined. The key information is present, but the duplication wastes space.

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?

Given 3 optional parameters and no output schema, the description lists the return fields (report date, timing, EPS estimates, etc.) and source, partly compensating for missing output schema. It is sufficiently complete for a data retrieval tool with no required params.

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% with clear parameter descriptions. The description adds value by providing a concrete example (date and days usage) that clarifies parameter interaction beyond what the schema states.

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 'US equity earnings announcement calendar' and lists the data fields provided (report date, timing, EPS estimates, market cap, etc.). This immediately distinguishes it from sibling tools like price, sentiment, or macro_calendar, which serve different purposes.

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 US equity earnings, but does not explicitly specify when to use this tool versus alternatives (e.g., macro_calendar for economic events, price for stock data). No 'when not to use' or alternative tool mentions.

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