Get all disaster events affecting a specific country.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results (default 50, max 100) | |
| country | Yes | Country name or ISO3 code | |
| daysBack | No | Number of days to look back (default 30, max 365) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It claims 'all' events, but the schema includes a limit parameter (default 50, max 100), making the claim misleading. It also fails to disclose the default 30-day lookback period or the meaning of 'affecting,' leaving key behavioral aspects undocumented.
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, front-loaded sentence with no unnecessary words. It states exactly what the tool does, making it highly concise and easy to parse.
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?
Without an output schema or annotations, the description must compensate by explaining result limits, time-window defaults, and the criteria for 'affecting.' The one-line description omits these critical details, leaving the tool underspecified for an AI agent to use correctly.
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 covers all 3 parameters with detailed descriptions (100% coverage). The tool description adds no additional parameter-level meaning, so the baseline of 3 is appropriate since the schema does the heavy lifting.
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+resource+scope: 'Get all disaster events affecting a specific country.' This clearly distinguishes it from siblings like get_active_disasters (active disasters) and search_events (general search), making the tool's purpose unambiguous.
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 country-filtered queries but does not explicitly state when to use this tool over alternatives like search_events. No exclusions or alternative recommendations are provided, so usage context is only implied.
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.
