Get wildfire statistics summary including total fires and acres burned.
Returns aggregate statistics from active incident data. When no year is
specified, returns current year statistics.
Args:
year: Year to get statistics for (e.g. 2025). Defaults to current year.
| Name | Required | Description | Default |
|---|---|---|---|
| year | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the disclosure burden. It clearly states that results are aggregate statistics from active incident data and explains the default-year behavior. This adequately covers the behavioral scope for a read-only stats tool, though it does not discuss edge cases like years with no data.
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 compact and front-loaded with the primary purpose, followed by return behavior and parameter guidance. The Args block slightly duplicates schema information, but it adds a concrete example and the default-behavior detail, so each sentence earns its place.
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?
This is a simple one-parameter tool with an output schema, so the description does not need to explain return values. It covers the core purpose, data source, and default year behavior. It does not explicitly address sibling-tool selection, but that is a usage-guidance gap, not an operational completeness gap.
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 schema only shows 'year' as an integer with a null default and no description. The tool description compensates with an Args block explaining that year is the target year (e.g., 2025) and defaults to the current year, adding meaningful semantics beyond the schema.
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 and resource: 'Get wildfire statistics summary' and explicitly mentions 'total fires and acres burned.' It clearly distinguishes this aggregate-summary tool from sibling tools like get_active_fires and get_fire_perimeters.
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 by describing aggregate statistics and the default to the current year, but it does not explicitly state when to prefer this tool over get_active_fires or get_fire_perimeters. No alternatives or exclusions are named.
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.
Each tool targets a distinct aspect of wildfire data: active fire incidents, fire perimeters, and aggregate statistics. There is no overlap or ambiguity between the tools.
All tools follow the pattern 'get_' followed by a descriptive noun in snake_case (get_active_fires, get_fire_perimeters, get_fire_stats). The naming is perfectly consistent and predictable.
With only three tools, the server is minimal but each tool serves a clear and necessary purpose for wildfire data retrieval. The count is well-scoped for the narrow domain.
The server covers listing active fires, retrieving perimeters, and getting statistics. A minor gap is the lack of a direct way to fetch detailed information for a specific fire by name, though perimeters can be looked up by name.