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

With readOnlyHint=true and openWorldHint=false already declared, the bar is lower. The description adds context beyond the annotations by summarizing exactly what metadata is returned and the ID convention. No contradiction with the annotations; the return-summary adds value over the safety profile alone.

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 sentences with zero waste: the core action with examples is front-loaded, the second sentence states what is returned, and the third gives usage guidance. Every 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?

For a single-parameter, read-only tool with an output schema present, the description is complete. The agent knows the ID format, what the tool returns, and when to invoke it; the output schema covers return structure, so no further detail is needed.

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 description coverage is 100%, so the baseline is 3. The description layers on the meaning of the ID prefixes (GHCND, COOP) and reaffirms the source via find_stations, adding modest interpretive value beyond the schema's own stationId description.

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?

States a specific verb and resource: 'Fetch full metadata for a single weather station by its ID.' It names concrete ID formats with examples, lists the return content (name, coordinates, elevation, date range), and is clearly distinguishable from siblings like noaa_climate_find_stations and noaa_climate_fetch_data.

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 an explicit workflow: use when you have an ID from noaa_climate_find_stations, for complete details or to verify a station before querying data. This gives clear when-to-use guidance and names the upstream sibling, but it stops short of an explicit when-not-to-use (e.g., directing raw data queries to noaa_climate_fetch_data).

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