get_solar_wind

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

With no annotations provided, the description carries full burden. It discloses the source satellites, data fields with units and coordinate system, and a practical use case. It does not specify data freshness, latency, or authentication requirements, but given the tool's simplicity, the transparency is adequate.

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?

Three concise sentences: first introduces source and data type, second details return fields and units, third adds context on usage. No redundant information, and key details are front-loaded.

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 tool's scope, the description covers source, output fields, and a use case. An output schema exists (not shown), so return structure is partially documented. Missing details like data update frequency or historical availability, but overall complete for a simple 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?

Schema coverage is 0%, so description must explain parameters. It mentions 'for the chosen window' but does not explicitly list the enum values or describe the window parameter. The enum values are in the schema, but the description adds minimal semantic value beyond that. 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 the tool retrieves real-time solar wind data from DSCOVR/ACE at L1, specifically magnetic field and plasma parameters. It distinguishes from sibling tools like aurora forecasts or Kp indices by focusing on raw solar wind measurements, making the purpose unambiguous.

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 implies use for monitoring solar wind conditions, especially for geomagnetic storm drivers, by mentioning Bz and speed. However, it does not explicitly state when to use this tool versus alternatives or when not to use it, though the sibling list provides context.

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