robinhood_get_earnings

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

No annotations are provided, so the description must disclose behavioral traits. It does not mention whether the tool is read-only, what data is returned (e.g., quarterly earnings, surprise factors), or any constraints like date range. A minimal statement like 'Returns earnings per share and revenue for recent quarters' would add transparency.

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 a single, concise sentence that is front-loaded and free of unnecessary words. Every word 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?

Given the presence of an output schema (not shown), the description does not need to detail return values. However, it lacks context about how earnings data relates to sibling tools and does not compensate for missing annotations. It is minimally complete for a simple lookup tool but feels lacking in a rich API with many similar endpoints.

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 has 100% coverage for the single 'symbol' parameter, with a standard description. The tool description adds no extra meaning beyond the schema. Baseline 3 is appropriate as the schema already documents the parameter adequately.

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 'Get earnings data for a stock,' which specifies the action (get), resource (earnings data), and scope (for a stock). It effectively distinguishes from sibling tools like robinhood_get_dividends or robinhood_get_fundamentals by naming a distinct data type.

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 on when to use this tool versus alternatives. With many sibling tools covering related financial data, the description should indicate contexts or criteria for selecting earnings data (e.g., 'Use for company earnings reports; for broader financial metrics, see get_fundamentals').

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