Güncel haber başlıkları: AA ve TRT Haber, kategoriye göre

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds meaningful context: data comes from an RSS feed, full article text requires following the link, and headlines are the publisher's expression. This goes beyond the annotations by explaining the source behavior and the need to fetch article content externally, with no contradiction.

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 compact and front-loaded with the core purpose, then covers parameter details efficiently. The English translation partly repeats the Turkish first sentence, which is mild redundancy, but overall every section 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 read-only headline-listing tool with an output schema, the description is complete: it covers all parameters, source-specific categories, defaults, filtering, and how to obtain full article text. No critical missing information prevents correct invocation.

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 coverage is only 50%, but the description compensates by fully specifying `kaynak` values, complete `kategori` lists per source, `ara` as a title/summary filter, and `limit` defaulting to 20. This is substantial added meaning beyond the sparse input schema.

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 specific verb and resource: retrieving latest headlines from AA or TRT RSS feeds, with title, summary, link, and publication time. It is clearly differentiated from sibling tools like kandilli_depremler or resmi_gazete_fihrist because it explicitly names its news sources and content fields.

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 gives explicit guidance on source and category selection, including the full category list for each source and the default source/category. It does not name alternatives or explicitly state when not to use it, but the context is clear enough for an agent to select the tool appropriately.

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