singapore_get_forecast_2h

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description adds genuine behavioral context about pagination (preserved upstream token, consuming local offsets), but 'Local limits apply to timestamp groups' is opaque jargon that an agent cannot act on confidently.

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?

It is short and front-loads the resource, which is good. However, the final two sentences are compressed into terse, hard-to-parse jargon whose meaning is not recoverable from the text, so brevity comes at the cost of clarity.

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 7 optional parameters, near-zero schema coverage, and a filter-oriented tool, the description should explain what area/region/station_id select and how limit/offset interact with pagination_token. Output schema exists, so return values need not be explained, but the filtering model remains unexplained.

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 only 14% (only date is documented), so the description carries the burden and largely fails. It clarifies date semantics ('Singapore local dates; latest if omitted') and hints at pagination_token, but area, region, station_id, limit, and offset get no added meaning beyond their names.

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 the resource precisely ('NEA 2-hour area forecasts'), and the '2-hour' qualifier distinguishes it from the sibling 24h and 4-day forecast tools. The retrieval verb is only implied, but an agent can identify the resource without opening the schema.

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?

'latest if omitted' gives one useful default behavior for the date parameter, but there is no guidance on when to pick this tool over singapore_get_forecast_24h or singapore_get_forecast_4day, and no exclusions are stated. Usage is implied rather than directed.

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