getEarningsReports

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the description adds context about the returned data fields (dates, EPS estimates, revenue projections). This is helpful but does not cover potential issues like missing data, rate limits, or pagination. The description 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 sentences, directly stating the purpose and data returned. No extraneous information, front-loaded with the action. Every sentence adds value.

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 simple read-only retrieval tool with a small schema (2 params) and no output schema, the description covers the main output fields (dates, EPS, revenue projections). It lacks details on result ordering or default limit behavior, but these are minor gaps. Overall, it provides enough context for an agent to understand what to expect.

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?

Input schema coverage is 100%, with both 'symbol' and 'limit' described clearly. The description adds minimal extra meaning beyond the schema; it mentions 'specific stock symbol' but that is already present. The limit parameter's default and max are in the schema but not in the description, so no additional value is provided.

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 it retrieves earnings information for a specific stock symbol, listing specific data types (dates, EPS estimates, revenue projections). This distinguishes it from sibling tools like getEarningsCalendar (which likely lists earnings dates for many stocks) and getEarningsTranscript (which provides full transcript text). The verb 'Retrieve' and resource 'earnings information' are specific and unambiguous.

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 does not provide any guidance on when to use this tool versus alternative earnings-related tools in the sibling list (e.g., getEarningsCalendar, getEarningsSurprisesBulk, getEarningsTranscript). There is no mention of when not to use it or what scenarios are appropriate, leaving the agent to guess.

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