Get current flood conditions for USGS monitoring sites in a state.
Returns sites where water levels are above flood stage, indicating
active flooding or near-flood conditions. Checks the most recent
instantaneous values against known flood stages.
Args:
state: Two-letter US state abbreviation (e.g. 'CA', 'TX', 'LA').
| Name | Required | Description | Default |
|---|---|---|---|
| state | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Since no annotations are provided, the description carries the full burden. It discloses that it checks 'the most recent instantaneous values against known flood stages', revealing the freshness and method. It doesn't mention side effects or permissions, but as a read-only query this is acceptable; it adds value beyond the schema.
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 only a few sentences, with the purpose first, followed by return behavior and parameter spec. Every sentence earns its place; no redundant or vague wording.
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?
Given the simple tool (1 param, no nested objects) and the presence of an output schema, the description covers all necessary contextual aspects: purpose, behavior, and parameter details. It is complete and self-sufficient.
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 the description compensates fully with 'state: Two-letter US state abbreviation (e.g. 'CA', 'TX', 'LA')'. This adds necessary formatting and examples, making the parameter semantics excellent.
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 starts with 'Get current flood conditions for USGS monitoring sites in a state', which is a specific verb+resource+scope. It distinguishes itself from siblings by focusing on flood stage exceedance, explicitly indicating 'sites where water levels are above flood stage'.
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 clearly implies this tool is for flood-specific queries ('active flooding or near-flood conditions'), giving strong contextual guidance. It doesn't explicitly mention alternatives or exclusions, but the context makes the intended use clear relative to siblings like get_water_levels.
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 serves a clearly distinct purpose: flood status, site discovery, and water level data. There is no overlap or ambiguity between the tools.
All tool names follow a consistent 'get_' + descriptive noun pattern (get_flood_status, get_sites_by_state, get_water_levels). The naming convention is uniform and predictable.
With only 3 tools, the server is tightly scoped and each tool earns its place. The count is appropriate for a focused monitoring data access server.
The tool surface covers the primary workflow: discover sites, retrieve water levels, and check flood conditions. No obvious gaps exist for the server's stated purpose.