news_search

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

With no annotations, the description carries full disclosure responsibility. It usefully discloses auth requirements, backend options, result limits, and snippet truncation behavior, but it does not mention rate limits, error behavior, or what the returned news results contain. For a non-mutating search tool this is acceptable but not rich.

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 compact two-line summary followed by a scannable Args list. Every line adds useful parameter or behavior information, with no filler and no repetition of schema-default information.

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?

Given six parameters, no annotations, and an output schema, the description covers the caller-facing details needed to invoke the tool correctly: all parameters, constraints, and the no-key requirement. It is nearly complete, though edge behavior such as rate limits and empty-result handling is left undocumented.

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 input schema provides only types and defaults, so the description must add the meaning of all six parameters. It does so for every parameter, including allowed ranges, region examples, timelimit values, backend choices, and the meaning of snippet_chars=0.

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 that the tool performs news search via DDGS with DuckDuckGo/Bing/Yahoo news backends and no API key. This clearly distinguishes it from image_search, video_search, and web_search siblings.

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 tool is positioned as a news-specific search, which implies it should be selected over web/image/video search, but it never explicitly states when to prefer it or when to choose a sibling. Usage guidance is inferred from the news focus rather than stated.

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