get_global_events

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

Discloses that results are sorted by Goldstein scale descending, capped at limit, and returns specific fields. Mentions GDELT's 15-minute update cycle. No annotations, so description carries burden; no destructive behavior implied.

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?

Six sentences across two paragraphs, front-loaded with purpose, all sentences add value: data source, scale, code options, sorting, limits, return fields. No fluff.

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?

No output schema, but description explains return fields (actor country codes, Goldstein score, article count, source URL). Lacks error handling or missing data mentions, but sufficient for intended use.

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 0%, but description fully explains country_code (code format), min_goldstein_scale (threshold with default), and limit (capping). Adds value beyond schema's type info.

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?

Clearly states the tool fetches recent high-impact GDELT 2.0 events for a country, explains the Goldstein scale, and describes output formatting. Distinct from siblings like check_network_anomalies and get_macro_alert.

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?

Provides clear instructions on using country codes (3-letter GDELT or 2-letter FIPS) and explains sorting and capping. Lacks explicit mention of when not to use this tool, but sibling tools are sufficiently different.

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