get_radarLatest NWS KHGX (Houston/Galveston) radar still image covering Crosby, TX, returned inline as a GIF. For the animated loop, see https://crosbynews.com/radar.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint. Description adds minimal extra: format (GIF) and source (NWS KHGX). Acceptable but not rich.
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?
Two sentences, no fluff. Front-loaded with purpose, second sentence provides alternative. Highly efficient.
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?
Adequate for a no-parameter, read-only tool. Missing potential details like image size or update frequency, but overall sufficient given simplicity.
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?
No parameters exist, baseline is 4. Description adds no parameter info because unnecessary.
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?
Clearly states it returns the latest NWS KHGX radar still image as a GIF covering Crosby, TX. Distinguishes from siblings like get_forecast or get_current_conditions by specifying location and format.
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?
Provides explicit alternative for animated loop via URL. Does not compare to sibling tools but gives clear context that this is for still images only.
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.
All tools have clearly distinct purposes: alerts, news, conditions, emergency contacts, forecast, radar, river levels, school events, traffic, and tropical outlook. There is no overlap or ambiguity.
All tool names follow the consistent pattern 'get_<topic>' using snake_case (e.g., get_alerts, get_forecast, get_radar). No deviations.
With 10 tools covering a broad range of local information (weather, alerts, news, emergency, traffic, schools, etc.), the count is well-scoped and each tool earns its place.
The tool set comprehensively covers the domain of local weather and community info for Crosby, TX: current conditions, forecasts, alerts, radar, river levels, tropical outlook, traffic, school events, news, and emergency contacts. No obvious gaps.