solar_history

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

The description mentions the data source (IONIS dataset, GFZ Potsdam and NOAA SWPC), time range (2000-2026), and indices returned. It implies read-only behavior without stating it explicitly. No annotations exist to cover safety, so description does well but could be more explicit about non-destructive nature.

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, no unnecessary words. First sentence clearly states the action and scope, second provides context and sibling differentiation.

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 output schema exists, description sufficiently covers purpose, data source, time range, and parameters. Could mention that dates must be in YYYY-MM-DD format (schema does), but overall complete for a query 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?

Input schema has 100% description coverage. The description adds value by naming the specific indices (SFI, SSN, Kp, Ap) and mentioning resolution options ('daily' or '3hour'), which is not fully detailed in schema descriptions.

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 it queries historical solar indices (SFI, SSN, Kp, Ap) for a date range, specifying the dataset and time frame. It distinguishes itself from the sibling tool solar_conditions for live data.

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 tells when to use this tool (historical data) and when not to (live current conditions), and provides a specific alternative tool name (solar_conditions).

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