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

Annotations already declare readOnly, idempotent and open-world, so the safety profile is covered. The description adds genuinely non-structured context: the tool is free, carries a cleared_with_attribution license, requires attribution to GDELT/UCDP/USGS/GDACS, and explicitly warns it is 'not for life-safety use' — a material usage caveat an agent would not otherwise know.

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 usage trigger is front-loaded, which is good, but the bulk of the text is a dense run-on of license names, attribution URLs and caveats stuffed into one sentence. The licensing information earns some place, yet it is compressed with the functional sentence rather than separated, hurting scannability.

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 read-only, zero-required-parameter filter tool with full schema coverage the calling mechanics are complete. However, there is no output schema and the description says nothing about the shape of returned incidents (fields, severity scale meaning, asset tag ordering, pagination or result caps), which is a real gap for an open-world data 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 100% and each of the four parameters (asset, region, since_hours, min_severity) including its enum, bounds and default is documented in the schema. The description only restates the asset vocabulary loosely, adding no format, matching or interaction guidance beyond the schema — baseline 3 applies.

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 states the resource concretely: recent geopolitical, conflict and natural-hazard incidents mapped to asset classes and liquid proxies, with examples of the proxies (oil, grains, gas, semis, gold, Treasuries, country ETFs). It never names a verb like 'list/return' and does not distinguish itself from siblings such as get_catalysts or get_macro_calendar, so a 4 rather than a 5.

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?

'Use this when you need recent geopolitical, conflict and natural-hazard incidents mapped to assets' gives a trigger condition, so usage is implied rather than absent. It offers no exclusions, no prerequisites, and no pointer to an alternative sibling tool for overlapping queries (catalysts, macro calendar), leaving routing to inference.

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