get_earnings

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

With no annotations, the description carries full burden. It describes the return structure (calendar, earnings_dates, estimate tables) but does not mention behavioral traits like read-only nature, rate limits, or required permissions. It adds value beyond the schema but lacks deeper behavioral details.

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 long, listing the main outputs concisely. It is front-loaded and efficient, though it could be slightly more structured (e.g., bullet points for the three return components).

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 the tool's simplicity (one parameter, no output schema), the description adequately covers the return structure. However, it omits prerequisites (e.g., valid symbol), error conditions, and data range limitations (e.g., how far back history goes). More context would improve completeness.

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 only parameter 'symbol' has no description in the schema (0% coverage). The tool description does not explain that 'symbol' is a ticker symbol, relying on the tool name. This fails to add meaning 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 calendar, dates, and estimates. It specifies the returned objects (calendar, earnings_dates, forward estimates) with details like reported vs estimated EPS and surprise percentage. This purpose is distinct from sibling tools such as get_analyst_data or get_financial_statements.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., get_analyst_data, get_financial_statements). The description only lists return values without contextual usage advice.

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