get_earning_dates

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 states the tool returns both upcoming and historical dates, but does not disclose any authentication needs, rate limits, data range limitations, or behavior nuances beyond the basic description.

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, concise sentence that contains no unnecessary words. It is front-loaded with the key action and resource.

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 the tool's simplicity and the presence of a clear input schema, the description is minimally adequate. However, it does not explain the output format or behavior (e.g., ordering, date range), which could be helpful for an AI agent. Adding a note about what the returned data looks like would improve completeness.

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?

The input schema provides descriptions for both parameters (symbol and limit) with 100% coverage. The description does not add additional meaning beyond what the schema already offers, such as clarifying how the limit applies to upcoming vs. historical dates.

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 the tool's function: 'Get upcoming and historical earnings dates for a stock.' It uses a specific verb and resource, and distinguishes it from sibling tools that focus on other financial data like analyst price targets or balance sheets.

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 the tool is for retrieving earnings dates, but does not provide guidance on when to use it versus alternatives like get_news for earnings reports. No explicit when-to-use or when-not-to-use context is given.

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