space_weather_grid_risk

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

With no annotations, the description carries the full behavioral burden, and it only discloses one trait: the data is 'live' (current rather than historical). It says nothing about update cadence, whether values are observed or forecast, units, or how GIC exposure is derived from Kp.

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?

It is a single compact phrase with no filler, so nothing is wasted. However, the brevity reflects under-specification rather than disciplined editing: it is a noun fragment, not a front-loaded statement of what the tool returns.

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 coordinate-driven tool with no annotations, no output schema, and undocumented parameters, the description is far too thin. It does not explain what the response contains, what units or index scale applies, or how the result should be interpreted.

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?

Two required parameters (lat, lon) exist with 0% schema description coverage, and the description never mentions them. It gives no format, units, coordinate convention, or valid range, so an agent has to guess how to supply a location.

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?

Names a specific resource and measurement: live geomagnetic activity (Kp) expressed as GIC / grid exposure. It is clearly distinguishable from the geological and water siblings, which deal with entirely different hazards. It lacks an explicit verb and never states that it returns a risk value for a coordinate pair, so it stops short of a 5.

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?

There is no statement of when to use this tool, when not to, or how it relates to siblings like seismic_hazard or ground_stability. The agent must infer usage entirely from the name and the fragment of description.

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