Robinhood Get Fundamentals

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only restates the action without explaining side effects, data source, limitations, or what constitutes 'fundamental data.' It implies a read operation but does not confirm read-only behavior or any other traits.

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, tight sentence with no filler or redundancy. It is concise, though it sacrifices useful detail and reads almost like a restatement of the tool name, which keeps it from a higher score.

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?

The tool is simple with one parameter and an output schema, so the description does not need to describe return values. However, it lacks any behavioral context around what fundamentals are included or how this compares with similar data-retrieval siblings, leaving a clear gap for an agent deciding which tool to use.

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 schema already covers the single parameter 'symbol' with a clear description, and schema description coverage is 100%. The description adds no additional meaning beyond the schema, so the baseline score of 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?

The description states a clear action ('Get') and resource ('fundamental data for a stock'), so an agent understands the core purpose. It does not explicitly differentiate itself from sibling data tools like quote, historicals, earnings, or ratings, aside from the inherent meaning of 'fundamentals.'

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 on when to choose this tool over sibling tools such as robinhood_get_quote or robinhood_get_historicals. There are no exclusions, prerequisites, or alternative routing instructions, leaving the agent to infer usage solely from the tool name and vague description.

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