noaa_stations

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

Annotations declare readOnlyHint=true, so the description is consistent. However, beyond that, the description adds no behavioral details such as pagination, rate limits, or output format. The description only says 'Search' which is already implied by the name.

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 concise at two sentences, front-loaded with the main purpose, and provides examples without unnecessary detail. Every sentence adds value.

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?

With 3 parameters, no output schema, and annotations, the description covers the main search functionality and gives example IDs. However, it does not mention the limit parameter or describe the output structure, which would be helpful for an API tool.

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 100%, so parameters are well-documented in the schema. The description adds example values for location_id and dataset_id, which provides helpful context, but does not significantly enhance understanding 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 clearly states it searches for NOAA weather stations by location or dataset. It provides specific examples of location IDs (FIPS:36, FIPS:06, CITY:US360019), which gives a clear purpose. However, it does not fully distinguish from sibling NOAA tools like noaa_climate_data or noaa_datasets, but it's still clear.

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 when to use this tool (search stations by location or dataset) and provides example location IDs, but it does not explicitly state when not to use it or suggest alternatives. Given the long sibling list, explicit guidance would help, but the examples provide some context.

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