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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), and the description adds substantial behavioral context beyond them: null semantics for unscheduled reports, variable history length, vendor units because Finnhub names no currency, drift reported as 'unavailable' rather than inferred, and the paid x402 cost model with free-allowance preservation.

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?

Front-loaded with the core purpose and dense with facts that each earn their place. The one flaw is redundancy: paid-only status is stated twice ('Paid-only, including the first call' and 'Hosted access: paid-only; each call costs $0.003 USDC...'), which slightly bloats an otherwise efficient block.

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?

With no output schema, the description carries the full burden of describing returns, and it does so thoroughly — enumerating the fields, their null/windowed behavior, and unit caveats. Combined with annotations covering safety, an agent has everything needed to call this correctly.

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%, so both parameters are already documented, including x_payment's challenge-then-retry flow. The description adds only marginal parameter-level value (the funds/ETF coverage caveat) and does not extend ticker syntax beyond the schema, so the baseline 3 is appropriate.

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?

States a specific verb ('Read') and resource ('earnings calendar and surprise history') scoped to a ticker, then enumerates the exact payload: next report date/session, estimates, latest reported EPS vs estimate with surprise percentage, and up to four quarters of history. This is clearly distinguishable from sibling tools like otto_equity_news or otto_financial_statements.

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?

Provides an explicit when-not ('Funds and ETFs have no earnings coverage') and repeats the paid-only prerequisite, which helps an agent decide whether calling is worthwhile. It does not, however, name an alternative sibling for the cases it doesn't cover, so routing guidance is incomplete.

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