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

With no annotations provided, the description must fully disclose behavior. It mentions the output includes beaten/missed/meet status and EPS, but does not reveal response format, pagination, rate limits, or what 'bulk' means in practice. It also doesn't state that 'year' is required or how the year is interpreted (fiscal vs. calendar).

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, but the second sentence ('offering valuable insights...') is promotional filler that adds no functional value. It is front-loaded with the core purpose but could be tightened to a single sentence without losing meaning.

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?

For a single-parameter tool with no output schema, the description provides a high-level understanding of the returned data. However, it lacks specifics about the response structure, the scope of 'multiple companies' (all companies?), and any limitations. It is adequate but not fully complete.

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 already provides 100% coverage with 'Year to get earnings surprises for,' so the baseline is 3. The description's use of 'annual' adds no new semantic detail beyond the schema; it doesn't specify format or validation rules.

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 bulk annual earnings surprises and provides actual vs. estimated EPS for multiple companies. It distinguishes itself from siblings like getEarningsReports or getEarningsCalendar by emphasizing 'bulk' and 'annual,' though it doesn't explicitly name alternatives.

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 related earnings tools. It only describes what the API does, not the intended use case or exclusions, leaving the agent to infer when this is the right choice.

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