gdelt_geo_events

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns event clusters with location, article count, and tone score, but does not mention authentication requirements, rate limits, or pagination behavior. The maxpoints parameter implicitly caps results, but this is not highlighted in the description.

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 two sentences (25 words), front-loaded with the action and API source, followed by the output details. Every sentence provides essential information without redundancy.

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 no output schema and no annotations, the description adequately explains the tool's purpose and returns. However, it does not detail the structure of clusters or address potential issues like query case sensitivity. For a simple parameter set, it is largely complete.

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 100%, so the schema already documents the three parameters. The description restates them in a narrative but adds no additional semantic meaning beyond the schema descriptions. Baseline 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?

The description clearly states the tool retrieves the geographic distribution of news events from the GDELT GEO API, specifying it returns clusters with location, article count, and tone score. This distinguishes it from sibling tools like gdelt_news_search (text search) and gdelt_tone_analysis (tone over time).

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 implies usage for mapping news events geographically but does not explicitly state when to use this tool versus alternatives like gdelt_news_search or gdelt_tone_analysis. No exclusion criteria or context for selection are provided.

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