yahoo_finance_ticker_earnings_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 mentions that results come from 'Yahoo Finance calendar HTML when Yahoo serves the table', implying conditional availability and HTML parsing. However, it does not disclose error handling, latency, or what happens if the table is not served. This is adequate but lacks depth.

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 sentence, which is concise. However, it includes a redundant phrase 'Yahoo Finance earnings dates' that could be omitted. It is front-loaded but slightly wordy.

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?

No output schema is provided, and the description only vaguely mentions 'standalone earnings-date rows' without detailing the return format. Given the complexity of parsing HTML, more information about the structure of returned data would be helpful. The description is insufficient for an agent to fully understand the output.

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 descriptions for all three parameters (symbol, limit, offset). The description adds no additional semantics beyond what the schema provides. Baseline is 3, and no extra value is added.

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 it returns earnings dates from Yahoo Finance calendar HTML. It uses the verb 'returns' and specifies 'standalone earnings-date rows', making the purpose clear. However, it does not explicitly differentiate from sibling tools like yahoo_finance_ticker_earnings or yahoo_finance_calendar, which could cause confusion.

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?

There is no guidance on when to use this tool versus alternatives. The description lacks any when-to-use or when-not-to-use instructions, leaving the agent to infer based on the tool name alone. No exclusions or prerequisites are mentioned.

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