get_financial_news

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

No annotations are provided, so the description carries the full behavioral burden. It helpfully discloses the data source (Yahoo Finance RSS) and freshness ('güncel'/'current'), but says nothing about rate limits, latency, caching, or error behavior for invalid tickers.

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?

Two sentences, zero filler, with the purpose front-loaded before the source and examples. Every element earns its place.

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 2-param read tool the description is adequate, but with no output schema and no annotations it does not describe what the returned news items contain (headline only, link, publish time). The 'limit' schema hints at headlines, but the return shape is left implicit.

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%, so both 'ticker' and 'limit' are already fully documented in the schema, including the same ticker format examples the description repeats. Baseline 3 applies since the description adds no meaning beyond the structured fields.

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?

States a specific verb ('döndürür'/returns) and resource ('güncel finans haberleri'/current financial news) scoped to stocks, indices, crypto and currencies. An agent can immediately distinguish it from data-oriented siblings like get_stock_history or get_fundamentals that return prices rather than news.

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?

Usage is implied by the description ('current news about an instrument') but there is no explicit when-to-use, when-not-to-use, or named alternative. With ~37 siblings, no routing guidance is offered even though news-based tools are a distinct category, leaving the agent to infer applicability.

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