Robinhood Get Earnings

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

Annotations are absent, so the description carries the full burden of explaining behavior. It only restates that this fetches earnings data; it does not disclose whether results are historical actuals, estimates, upcoming dates, or what fields will be returned. No output schema exists to fill this gap.

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 one short sentence with no filler and is front-loaded with the action. It is structurally concise, though the brevity contributes to the lack of context.

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 no output schema and no annotations, the description is not complete enough. 'Earnings data' is ambiguous and could mean earnings dates, EPS estimates, reported results, or a calendar. An agent can invoke the tool correctly with the symbol, but cannot anticipate what the response will contain or how to interpret it.

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 single parameter 'symbol' is already fully described in the input schema, and schema description coverage is 100%. The description adds no meaning beyond what the schema provides, so the 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 uses a clear verb ('Get') and resource ('earnings data') and names the target ('a stock'), so it is not a tautology. However, 'earnings data' is broad and does not distinguish it from siblings like robinhood_get_fundamentals or robinhood_get_ratings.

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 given about when to use this tool versus the many sibling tools. An agent must infer that 'earnings data' is distinct from fundamentals, news, ratings, or dividends without any explicit context or exclusions.

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