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

Annotations already establish readOnlyHint, idempotentHint, openWorldHint, and non-destructive behavior. The description adds meaningful behavioral context by explaining what each type actually returns (observed vs normals for reports; actually set records for records) and by showing example filter combinations. It does not contradict the 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?

The description is compact and front-loaded: it starts with the core resource, immediately distinguishes the two type modes, then lists filters, and finishes with concrete JSON examples. Every sentence contributes value and the examples make invocation behavior unambiguous.

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?

Given the rich schema with full parameter documentation, strong annotations, and an output schema, the description is complete enough for an agent to call this tool correctly. It covers the key selection logic between reports and records, available filters, and representative example calls. Nothing critical is missing.

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?

The input schema already has 100% description coverage for all eight parameters, including formats, constraints, and type-specific applicability. The description reinforces wfo format and date format and gives examples, but it does not add substantial meaning beyond the schema. Baseline 3 is appropriate.

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 that this tool returns NWS daily climate data, and explicitly breaks out the two modes: type=reports returns CLI daily climate reports (observed values vs normals) and type=records returns RER record event reports. This makes the resource and the distinction between report types clear, and it differentiates the tool from climate-normals-focused siblings.

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 gives clear usage context by listing allowed filters (wfo, station, date, start/end range, hours lookback) and provides two concrete examples showing valid payloads. It does not explicitly name alternatives or state when not to use this tool, but the scope is clear enough for an agent to select it appropriately.

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