duckduckgo_news_search

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

Description discloses key behaviors: default max 3 articles, excerpt length 150 chars, ability to override limit. No annotations exist, so description carries full burden. Missing details on error behavior, rate limits, or side effects.

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 concise sentences with no redundant information. Front-loaded with purpose and key details. Every word serves a purpose.

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?

Covers core functionality but omits explanation of time filter, safeSearch, and deprecated 'count'. No output schema provided, so return format beyond excerpts is unclear. Not fully complete for 5-parameter tool.

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 100% and already describes all parameters. Description adds value only for 'limit' (override). Other params like time, count, safeSearch are not explained beyond schema, so baseline of 3 is appropriate.

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?

Description clearly states it is a news search via DuckDuckGo and specifies return format (max 3 articles, 150-char excerpts). Sibling tool 'duckduckgo_web_search' is distinguishable by name, but no explicit differentiation is given.

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?

Provides guidance on default behavior and how to adjust result count using 'limit' param. However, lacks explicit when-to-use vs. web search and no exclusions or alternatives mentioned.

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