nws_radar_stations

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

The description adds useful behavioral context by listing the kind of data returned (station IDs, names, types, and coordinates). The readOnlyHint annotation already signals a safe read operation, and the description enriches that without contradicting it.

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 two short sentences: the first states the action and scope, the second enumerates the output fields. Every word contributes value and there is no unnecessary detail or redundancy.

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 zero-parameter list tool with a readOnly annotation and no output schema, the description covers purpose, scope, and result content. A mention of potential pagination or output format would improve completeness, but it is not essential for this simple 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?

There are no parameters in the schema, so parameter semantics are not a concern. The baseline for zero-parameter tools applies, and the description's mention of returned fields provides sufficient semantic context.

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 a specific verb ('List'), a specific resource ('NWS radar stations'), and geographic scope ('across the U.S.'). It distinguishes itself from sibling tools like nws_stations by focusing on radar stations.

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 sets the context for when to use this tool: when a list of NWS radar stations in the U.S. is needed. It does not explicitly mention alternatives or exclusions, but for a simple zero-parameter list tool its usage is readily inferable.

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