Robinhood Get News

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It clarifies that the tool returns news articles, but it does not define what 'recent' means in terms of time window, limits, ordering, or output shape. For a simple read-only endpoint this is acceptable but not rich.

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, front-loaded sentence with zero wasted words. It states the action, the result type, and the subject of interest efficiently.

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: one required parameter and no nested objects or output schema. Yet because there is no output schema and no annotations, the description leaves the return structure and recency semantics unspecified, making it adequate but incomplete.

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?

Schema description coverage is 100%, with 'symbol' described as 'Stock ticker symbol.' The description repeats the symbol concept via 'for a stock' but adds no additional meaning beyond the schema, 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 the specific verb 'Get' and a clear resource, 'recent news articles for a stock.' It distinguishes itself from all sibling tools, which target quotes, fundamentals, options, portfolio data, and other non-news resources.

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 implies the obvious use case: retrieve recent news when you have a stock symbol. However, it does not explicitly state when to use it versus alternatives and does not mention any exclusions or edge cases, though no sibling appears to fill a news role.

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