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

Annotations already establish readOnlyHint and openWorldHint, yet the description adds substantive context beyond them: refreshed every 5 minutes, and 'blocks NOAA did not deliver say ok=false' tells the agent how partial failure is represented in the payload. The observed-vs-forecast distinction further bounds interpretation of returned values.

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?

Front-loads the domain and source, then packs the returned fields into a compact list with the caveats trailing. It is dense but nearly every clause carries information; only the standalone 'Free.' opener is arguably dispensable.

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 no output schema, the description carries the return-value burden and does so by enumerating each data block plus the ok=false failure convention. Provenance, freshness, and interpretation limits are all covered, so an agent can call it correctly without further context.

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 the baseline is 4 and there is nothing for the description to clarify beyond the empty schema. No parameter-level gaps exist.

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 resource and enumerates exactly what it returns: Kp index (now and 24h max), NOAA G/R/S scales, solar wind speed and density, and M/X flares from the last 24 hours. The named source (NOAA SWPC) and the explicit scope make it unmistakable against siblings like get_earthquakes or get_crisis.

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 clear negative guidance — 'not a forecast and not an assessment of effects on a specific system' — which prevents the agent from over-claiming with the data. It stops short of naming an alternative tool for forecasting or impact assessment, so the routing is implicit rather than explicit.

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