NOAA Latest Observation (US)

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate readOnly, non-destructive, idempotent, openWorld. The description adds provenance (NOAA NWS) and geographic limitation, but does not disclose potential behavior like 'returns null if station not nearby' or data freshness. Moderate additional value beyond annotations.

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?

Three concise sentences: purpose, return fields, provenance/constraint. Every sentence adds value without fluff. Front-loaded with verb and resource.

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?

The tool is simple with two params and an output schema. The description covers what is returned and the geographic constraint. It could mention what happens for invalid locations, but overall sufficiently complete for the intended use.

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?

Both parameters have schema descriptions with bounds, achieving 100% coverage. The description reinforces the US-only constraint but adds no new syntax or format details. Baseline 3 is appropriate as schema handles semantics.

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 clearly states the verb (Get), the resource (latest weather observation from nearest ASOS/AWOS station), and geographic scope (US contiguous). It also lists specific return fields, distinguishing it from siblings like noaa.weather.forecast.

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 current observation at US locations but does not explicitly mention when to use alternative tools (e.g., forecast or hourly) or when not to use this tool. The geographic constraint is clear but no guidance on selection among siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.