Get list of recent disaster alerts from the last N hours.
| Name | Required | Description | Default |
|---|---|---|---|
| hours | No | Number of hours to look back (default 24, max 168) | |
| minAlertLevel | No | Minimum alert level: 'green', 'orange', or 'red' |
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 the temporal scope and that the result is a list, but does not mention sorting, empty result behavior, or the filtering effect of minAlertLevel. This is minimal but not misleading.
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 a single sentence that states the purpose without redundancy. Every word contributes meaning, making it highly concise and well-structured.
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 simple tool with two optional parameters and no output schema, the description is minimally adequate. It clearly states the tool's function but omits return format details and the behavior of minAlertLevel, relying on the schema to fill these gaps.
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?
The input schema provides 100% coverage with descriptions for both 'hours' and 'minAlertLevel', including defaults and valid values. The description adds no additional parameter context, aligning with the baseline of 3 for high schema coverage.
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 uses a specific verb 'Get' with a clear resource ('list of recent disaster alerts') and a temporal scope ('last N hours'). This distinguishes it from sibling tools like get_active_disasters (active vs. recent) and search_events (search vs. list).
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 the tool is for retrieving recent alerts within a time window but does not explicitly state when to use it over alternatives like get_active_disasters or search_events. There are no stated exclusions or alternative tool references.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly distinct: get_event_data retrieves a single event, search_events lists events with filters, and reference tools like get_alert_level_info and get_event_types are obviously different. However, get_active_disasters, get_recent_alerts, and search_events have some overlap in returning lists of events, though their descriptions clarify the specific time-based or filter-based focus.
Seven of eight tools follow a consistent get_<noun> pattern (get_active_disasters, get_event_data, etc.), making them predictable. The single deviation is search_events, which omits the 'get_' prefix but still uses a clear verb-noun structure.
With 8 tools, the set is well-scoped for a disaster information API. Each tool serves a distinct query purpose—reference data, single-event details, list queries, and statistics—without unnecessary redundancy or bloat.
The tool surface covers the core read-only operations expected for this domain: listing active/recent events, searching with filters, fetching details, retrieving by country, and accessing reference data (alert levels, event types) plus statistics. There are no obvious dead ends or missing operations for a query-focused API.
