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

With no annotations provided, the description carries the full burden, but it only restates high-level output types (dates, estimates, projections). It does not disclose behavior such as pagination, time range covered, result ordering, or whether the data is historical or upcoming. This is insufficient for a tool with no other behavioral metadata.

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 two sentences with a clear front-loaded verb and no redundant schema repetition. The closing phrase 'to help you stay on top of company performance' is marketing fluff that adds no operational value, slightly reducing conciseness.

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 no output schema and no annotations, the description provides a reasonable overview of the tool's purpose and return fields but lacks critical operational details: it does not specify whether results are a list or single object, how reports are ordered, what time period is covered, or how the 'limit' parameter behaves in relation to the number of available reports.

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% (both symbol and limit have descriptions), so baseline is 3. The description adds context about symbol being a specific stock and enumerates the returned metrics, but it does not clarify how the 'limit' parameter affects which reports are returned, nor does it provide any formatting or constraint details beyond the schema.

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 retrieves earnings information for a specific stock symbol and lists concrete data types (earnings report dates, EPS estimates, revenue projections). It uses a specific verb-resource pairing ('Retrieve... Earnings Report API'), but does not explicitly distinguish itself from sibling earnings tools like getEarningsCalendar or getEarningsSurprisesBulk.

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 used when you need in-depth earnings data for a specific symbol, but provides no explicit guidance on when to use it over alternatives, nor any exclusions. No comparison to sibling tools like getEarningsCalendar is offered.

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