getEarningsSurprisesBulk

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

Annotations declare readOnlyHint, idempotentHint, openWorldHint, so behavioral safety is covered. The description adds value by specifying the data content (actual vs estimated EPS, multiple companies, annual). It does not contradict 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 description is two concise sentences that front-load the purpose. No redundant or extraneous information; every sentence earns its place.

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 one parameter, good annotations, and no output schema, the description sufficiently explains the output as 'actual versus estimated EPS for multiple companies'. It provides enough context for an agent to understand the tool's function and return type.

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 description coverage is 100%, but the description does not add extra meaning to the 'year' parameter beyond the schema's minimal description. No format or range details are provided, so baseline score of 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?

The description clearly states the tool retrieves bulk data on annual earnings surprises, comparing actual vs estimated EPS for multiple companies. The verb 'retrieve' and resource 'bulk data on annual earnings surprises' are specific, and it is distinct from siblings like getEarningsCalendar or getEarningsTranscript.

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 use for quick analysis of multiple companies' earnings surprises but lacks explicit when-to-use or when-not-to-use guidance compared to alternatives. No exclusions or alternative tool suggestions are provided.

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