search_articles

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

With no annotations, the description covers key behaviors: search capabilities (Boolean, phrases), time range (3 months back), and default behavior (50 most recent articles from past month). It doesn't mention rate limits or auth but these are acceptable for a search tool.

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 sentences, no wasted verbiage. The description is front-loaded with purpose and quickly covers key features and defaults.

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?

The description explains core functionality but fails to mention what fields the returned articles contain. With no output schema, this is a gap for an agent needing complete understanding of tool output.

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 baseline is 3. The description adds value by explaining that the query parameter supports Boolean operators and giving default context for maxRecords and timespan (50 most recent, past month).

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 states the tool searches GDELT's global news database for articles across 65 languages, specifying verb and resource. It distinguishes from sibling tool search_images by focusing on articles.

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 provides context for when to use (searching news articles) but does not explicitly contrast with alternatives or state when not to use. The sibling tool name suggests different content type, so context is clear.

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