get_nowcast_forecast

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It mentions 'queries' which indicates a read operation, and specifies the 6-hour forecast horizon, providing some context. However, it does not mention any potential side effects, authentication requirements, or coordinate system details, which leaves gaps in behavioral transparency.

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?

The description is a single clear sentence that is front-loaded with the key action and resource. It contains no unnecessary information.

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 low complexity of the tool (two number parameters, output schema present), the description covers the essential purpose and context (6-hour forecast at a coordinate). It could be more complete by noting the coordinate format or that it is read-only, but these are partially implied by 'queries' and the output schema.

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?

The input schema has two parameters (lat, lon) with no descriptions, and the description adds only that it targets a 'specific coordinate' without explaining the format, units, or ranges. This minimal addition fails to compensate for the 0% schema description coverage.

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 the tool 'queries' the 'very short-term (6-hour) forecast' for 'a specific coordinate', using a specific verb and resource. It distinguishes from siblings by specifying the 6-hour horizon, which sets it apart from observations or longer-term forecasts.

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 very short-term forecasts but does not explicitly mention when to use it over the sibling tools like get_nowcast_observation or get_short_term_forecast. There are no exclusion criteria or alternative recommendations, so usage guidance is only implicit.

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