climate_anomalies

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

No annotations are provided, so the description bears the full behavioral burden. It does add genuine methodological context: the baseline is a 5-year same-window comparison and coverage is limited to country centroids. But it says nothing about read-only behavior, latency, whether results are cached, how time windows are selected (no time parameter exists), or how coarse the centroid resolution is.

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?

Tight and front-loaded: the core subject and baseline method come first, with scope second. No filler. Slightly fragmentary phrasing rather than a complete sentence, but nothing is wasted.

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?

An output schema exists, so return-value explanation is not required. But for a tool with an undocumented parameter, no annotations, and an opaque geographic scope ('conflict-dense country centroids'), the description leaves meaningful questions unanswered for an agent deciding whether and how to call it.

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?

There is exactly one parameter, 'detail', with a default of 'short' and 0% schema description coverage and no enum. The description never mentions it, so an agent cannot know what values are allowed or what effect the choice has. This is the one place a short sentence would have paid off, and it is absent.

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 identifies the resource (temperature/precipitation anomalies) and the comparison method (vs. a 5-year same-window baseline) over 'conflict-dense country centroids'. However, it is a bare noun phrase with no verb and no explanation of what 'over conflict-dense country centroids' means operationally (Is it a fixed global set? Per-country rows?). It also does not distinguish itself from the sibling 'anomalies' or 'area_baseline' tools, leaving ambiguity about which to choose.

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?

No guidance on when to use this tool, when not to, or which sibling tool covers similar but different needs. Given siblings named 'anomalies' and 'area_baseline', the absence of any routing guidance is a real gap.

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