netintel_weather_current

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

No annotations are supplied, so the description carries the full burden. It usefully discloses that city names are geocoded server-side and lists the output payload, but it never states default units (the text is cut off at 'metric…'), behavior when both city and coordinates are passed, or whether caller-supplied coordinates bypass geocoding.

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?

Front-loaded with the core capability and the most important invocation detail, with no filler sentences. It loses a point because the text is visibly truncated mid-clause ('No API key, metric…'), signaling omitted content rather than deliberate brevity.

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?

With no output schema, the description correctly summarizes return fields, which is the right call. But with no annotations and a truncated trailing clause, it omits default units and the distinction from netintel_weather_forecast — gaps an agent must guess around.

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 the description must compensate. It clarifies the two input modes (city name, auto-geocoded, vs. explicit coordinates), which adds real meaning for three of four params, but the 'units' parameter is never explained — its enum-less schema gives no clue either.

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?

States a specific verb+resource ('Live weather + 3-day forecast') and enumerates the returned fields, so an agent knows exactly what it produces. However, it never distinguishes itself from the sibling netintel_weather_forecast, which overlaps on the forecast portion, leaving ambiguity about which to pick.

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?

It tells how to invoke ('Give a city name ... or coordinates') but not when to prefer this over netintel_weather_forecast or any alternative. There are no exclusions or conditions, only implied usage context ('any city or lat/lon worldwide').

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