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 correctly implies a read-only query and describes the return content, but does not mention pagination, rate limits, or data freshness. The behavior is adequately transparent for a simple data fetch 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, front-loaded with the core action and followed by output details. Every sentence earns its place with no extraneous words.

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 3 parameters, no output schema, and no annotations, the description provides sufficient context about purpose and return fields. It could be more precise about data format (e.g., tone score range), but is adequate for tool selection.

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%, with clear descriptions for each parameter. The description adds meaning by specifying the output structure (clusters with location, article count, tone score) beyond the schema, which has no output schema defined.

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 verb 'Get geographic distribution', the resource 'news events for a topic from the GDELT GEO API', and the return shape 'event clusters with location, article count, and tone score'. It distinguishes from sibling tools like gdelt_news_search and gdelt_tone_analysis.

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 geographic mapping of events but does not provide explicit guidance on when to use it versus alternatives. It lacks when-not-to-use conditions or direct sibling references.

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