weather_current

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so the safety profile is fully covered. The description adds genuinely useful context — the provider and that no authentication/API key is needed — but says nothing about units (metric vs imperial), rate limits, or what happens with an invalid coordinate.

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?

A single front-loaded sentence with no wasted words; the verb/resource lead and the no-API-key note follows. Nothing to trim.

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 should say what comes back (temperature, wind, conditions, units), and it does not. It is complete enough to attempt a call, but an agent cannot know the response shape or unit system without invoking 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?

Schema description coverage is 0%, so the description carries the full burden for three parameters and adds nothing. Latitude/longitude are largely self-describing by name, but the expected format (decimal degrees vs DMS), valid ranges, and the meaning of the optional timezone field (IANA name, "auto", or default to UTC) are left entirely undocumented.

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 and resource ("Get current weather for a location") plus the data source and the notable absence of an API key requirement. The word "current" implicitly separates it from weather_hourly/weather_forecast, but those siblings are never named, so differentiation is inferred rather than stated.

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?

"Current" implies the use case (present conditions, not forecasts or historical), which is enough for an agent to pick it over weather_forecast or historical_weather. However, there is no explicit when-to-use statement, no prerequisites, and no mention of alternatives or coordinate-resolution helpers like nominatim_search.

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