get_news

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It only says 'recent news' without explaining response shape, pagination/limit behavior, time window, or any rate-limit/auth considerations. Nothing contradicts the tool name, but the behavioral context is minimal.

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 sentence with no filler and gets the core purpose across quickly. However, its brevity is partly due to omitted behavioral and parameter context, so it earns high but not perfect marks for structure.

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?

For a tool with no output schema and no annotations, this description is not complete enough: it does not describe the returned news items, fields, ordering, or how to control recency. The two params are simple, so this is a modest gap, but the absence of return-value information makes it 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?

The schema covers the symbol parameter with an example, and limit has default/range constraints, but the description adds nothing about how 'limit' behaves or what 'recent' means in terms of the response. With only 50% schema coverage and no clarification in the description, the missing parameter semantics are not compensated.

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 specific verb ('Get') and resource ('recent news for a stock'), which conveys the core function unambiguously. It is clear enough to separate it from sibling quote, bars, financials, and events tools, though it does not explicitly name alternatives.

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 choose this tool over sibling tools such as get_company_events or get_analyst_actions. The description only states what it does, not the context or exclusions, leaving the agent to infer usage.

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