get_news_sources

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

With no annotations, the description carries the burden and does disclose the return shape (a tree structure of engine types and sub-categories). It does not state whether the call is read-only or describe any side effects, safety, or limits, leaving some behavioral ambiguity.

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?

Three compact sentences: purpose, return structure, and workflow advice. Every sentence adds value and the key claims are front-loaded.

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 zero-parameter metadata-discovery tool, the description explains what is returned and why it should be called first. It lacks a detailed schema of the tree, but it provides enough context for 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?

The tool takes no parameters, so the schema fully covers parameter semantics; the description doesn't need to add parameter meaning. Baseline for a zero-parameter tool is 4.

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 identifies the resource: all available news source categories plus metadata, with engine types and examples (Bloomberg, Reuters). It is unambiguous versus the search/latest-news siblings, though it doesn't explicitly distinguish itself from the similarly named list_news_types.

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 states when to call the tool: 'Use this first... before searching.' This gives an explicit workflow context but doesn't name alternative tools or exclusion conditions, so it's clear but not fully comprehensive.

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