Solar Forecast

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds genuine value beyond that: the upstream source (NOAA) and the fact that these are predicted, not observed, values over a 27-day window. It does not mention refresh cadence, caching, or behavior on upstream failure, which keeps it below a 5.

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?

Two short sentences, front-loaded with what is returned and followed by use cases. No filler, no restatement of the title, and every clause carries information an agent can act on.

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?

An output schema exists, so return structure needn't be described, and the description already names the key forecast fields (SFI, Kp). For a zero-parameter, read-only forecast tool this is everything an agent needs to select and call it correctly.

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 tool takes zero parameters, so there is no parameter semantics to explain; the baseline of 4 applies. The description correctly implies a no-argument call by framing the output purely as a fixed forecast window.

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 (NOAA 27-day solar flux and geomagnetic forecast) and immediately names the data returned (predicted SFI and Kp values). The explicit 27-day forecast horizon distinguishes it from current-condition siblings like solar_conditions, solar_wind, and solar_xray without needing to name them.

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?

Gives concrete use cases ('planning DX operations, contests, and POTA/SOTA activations'), which tells the agent when this tool is the right pick. It stops short of naming alternatives or stating when not to use it (e.g., versus solar_band_outlook or solar_conditions), so it falls short of a 5.

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