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

Beyond readOnlyHint=true, the description discloses genuinely important behavior: page size of 25, a default one-day search window when from_date/to_date are omitted, default sort behavior, and the OR-within/AND-across logic for list filters. These are the exact traps an agent would otherwise hit.

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?

Four sentences, each carrying distinct information: return shape, ranking defaults, default date window, and filter composition. The most consequential constraint (one-day default) is stated plainly rather than buried.

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?

With 16 optional parameters and no output schema, the description does the necessary work: it describes the return payload and the filter algebra. Minor gaps remain around pagination limits beyond the schema's maximum and what an empty result looks like, but nothing blocking.

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%, so the baseline is 3, but the description adds real meaning on top: that filters take lists, values within one filter are OR, and different filters AND together, plus the default date range. That combination semantics is not visible in the 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 opens with a specific verb and resource ("Search news articles from publishers worldwide") and states the return shape (25 articles per page with publisher and URL). It references helper siblings get_coverage and get_sources, but never contrasts itself with get_latest_news, leaving that sibling relationship to inference.

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?

It explains the selection logic well: with keywords or title the best matches come first, otherwise the newest, and sort can override. It also routes agents to get_coverage and get_sources for valid codes. What's missing is an explicit "use get_latest_news instead when…" exclusion.

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