getEarningsReports

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety profile is covered. The description adds only a hint of returned content (dates, EPS estimates, revenue projections) but no pagination behavior, history depth, or what happens with the limit parameter, so extra value beyond annotations is modest.

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?

Two sentences, front-loaded with the verb, but padded with marketing filler ('in-depth', 'Gain access to', 'help you stay on top of company performance') that consumes space without informing tool selection.

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?

There is no output schema, so the enumeration of returned fields is genuinely useful and partially compensates. However, for a tool sitting among many earnings-adjacent siblings, the definition does not clarify scope (historical quarterly reports vs. calendar vs. surprises), leaving a real gap.

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% and both parameters (symbol, limit with default 100 / max 1000) are documented in the schema. The description mentions the symbol scoping but adds no format or semantic detail beyond the schema, so the baseline 3 applies.

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?

Names a specific verb ('Retrieve') and resource ('earnings information' / 'Earnings Report API') and enumerates content: earnings report dates, EPS estimates, revenue projections. It does not differentiate from nearby siblings like getEarningsCalendar, getAnalystEstimates, or getEarningsSurprisesBulk, leaving the agent to guess which earnings-flavored tool is right.

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?

'for a specific stock symbol' implicitly signals the per-symbol use case, but there is no explicit when-to-use or when-not-to-use guidance and no mention of the alternatives in a sibling list dense with earnings tools (calendar, surprises, transcript).

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