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

Annotations already carry the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the bar is lower; the description adds value beyond them by naming the data source (Yahoo Finance via yfinance), stating that no API key is required, and specifying the three output sections. Minor gaps like rate limits or data freshness are unaddressed, but nothing contradicts the 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 core operation is front-loaded in the first sentence, followed by a compact bulleted usage list and a one-line output/source note. Every sentence earns its place; the three usage bullets are slightly redundant with one another but the overall structure is clean and scannable.

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 that an output schema exists and annotations cover the safety profile, the description provides what an agent needs: the returned sections, concrete use cases, and access requirements (no API key). It omits behavior like how limit defaults work, but the schema documents 'limit', so remaining gaps are minor for a straightforward read-only fetch tool.

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 description adds no parameter-level guidance — it never mentions the symbol or limit fields. The nested EarningsParams schema does document symbol and limit well, which mitigates the low 0% coverage signal, and the usage bullets imply a ticker is the central input, but the description itself does not compensate for the coverage gap.

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 opening sentence names a specific verb and resource — fetching earnings history (EPS actual vs estimate, surprise %) plus upcoming earnings dates with consensus estimates — which is concrete and actionable. It also mentions forward EPS estimates by quarter and fiscal year, making the scope precise enough to distinguish it from siblings like GetDividendsAndSplits, GetFinancials, or GetAnalystRatings.

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 'Use this tool when' section lists three concrete scenarios (performance vs EPS expectations, next earnings date/consensus, surprise trends) that map directly to the tool's outputs. It does not name alternatives or state when not to use it, stopping short of the explicit exclusion guidance that would earn a 5.

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