get_ticker_news

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. It communicates that the tool performs a read-only fetch and returns news article fields, which is useful. However, it leaves 'recent' vague and does not mention pagination, sorting, time windows, or behavior for invalid symbols.

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 with the core verb and object front-loaded. It contains no filler, no tautology, and every word adds meaning.

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 simple one-parameter read tool with an output schema present, the description covers the essential purpose and return contents. The main gaps are the undefined meaning of 'recent' and missing details about article count or pagination, but these are minor given the tool's simplicity.

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 documents the only parameter, 'symbol', as 'The stock symbol', achieving 100% coverage. The description adds no format, validation, or examples beyond that, but none are necessary given the high schema coverage.

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 the action ('Fetches'), the resource ('recent news articles'), and the scope ('related to a specific stock symbol'), and even lists the returned content ('title, content, and source details'). This makes it easily distinguishable from sibling tools like get_ticker_info, get_price_history, and search.

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 tool should be used when news for a particular stock symbol is needed, but it does not explicitly state when to prefer this tool over alternatives like 'search' or 'get_ticker_info'. No exclusions or alternative conditions are mentioned.

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