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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true and idempotentHint=false, so the safety profile is covered. The description adds nothing beyond that: no data source, no forecast horizon limits, no rate limit, and no explanation of how 'past_hours' interacts with 'hours' – a real behavioral gap for a weather query.

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 tight clause, front-loaded with the core capability and the returned variables. Nothing is padded, though the terseness contributes to the semantic gaps elsewhere.

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 four-required-parameter, no-output-schema tool, the description should at minimum clarify the two time parameters (hours vs past_hours) and coordinate format. It does neither, leaving the caller to guess at the most consequential inputs.

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% across four required parameters. 'any point' loosely maps to lat/lon and 'hour by hour' loosely maps to hours, but past_hours – the parameter most likely to be misused (this tool unusually mixes past and future hours, hence idempotentHint=false) – is never explained, nor are units or bounds for hours.

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?

It conveys the resource (hourly weather readings at a coordinate) and lists the variables returned (temperature, rain, wind, cloud), but the verb is implicit and there is no explicit contrast with its close siblings cell_weather_grid and cell_weather_clouds. An agent can guess it's a point forecast but cannot be certain how it differs from the grid variant.

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 when-to-use guidance, no mention of alternatives among the three weather siblings, and no prerequisite or cost information. The phrase 'for any point' is the only implied usage condition.

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