Get recent space weather alerts

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

With no annotations, the description carries the full burden. It discloses ordering ('most recent first'), response contents (type code, UTC issue time, short extract not full text), and scoping ('active'). However, it doesn't define 'active' or mention any read-only status explicitly, though it's implied by 'Returns'.

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 sentences, purpose-led, with examples and usage notes. Every word earns its place; no fluff.

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 simple one-parameter tool with no output schema, the description covers purpose, return format, ordering, and usage context. The missing default is covered by the schema. Adequately complete.

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% with the 'limit' parameter clearly documented (maximum 75, default 5). The description references 'N' but adds no new semantic detail about the parameter beyond what the schema provides, so 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?

Clearly states it returns the N most recent active NOAA/SWPC space-weather alerts, watches, and warnings, with specific examples (geomagnetic K-index warnings, radio blackout alerts). This distinguishes it from sibling tools that provide forecasts, indices, or flux readings.

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?

Explicitly provides trigger phrases: 'Use this when asked 'any space weather warnings right now', 'is there a solar storm alert', or 'what's the latest SWPC bulletin'. This gives clear guidance on when to select this tool over alternatives.

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