Search news events

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so safety and determinism are covered. The description adds the cross-language nature of event clusters, which hints at multilingual results, but says nothing about pagination, result shape, or the token cost implied by the archive window.

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 short sentences, front-loaded with the definition of an event before the use-case hint. No filler or repetition of the title.

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 29-parameter, no-output-schema tool this is thin: the agent gets a definition of events but no sense of the returned structure (clusters, summaries, counts) or the practical cost/pagination considerations. The schema carries parameter detail, but the description leaves notable gaps for a complex 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 description coverage is 83%, so the schema already documents nearly all 29 parameters, including the time-window and filter semantics. The description only says filters are the same as article search, adding no new parameter meaning, which matches the baseline for high coverage.

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 a specific verb (search) and resource (events), and uniquely defines the resource as 'clusters of articles (often across languages) reporting on the same real-world happening.' This definition is what lets an agent distinguish it from newsapi_search_articles, which is named explicitly.

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?

Offers usage context ('good for what happened around X' and spotting broad coverage), which is helpful but not a routing decision. It never states when to prefer this over newsapi_search_articles or newsapi_get_event, so the agent must infer the choice from the definition of an event.

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