singapore_get_forecast_4day

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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered. The description adds pagination behavior ("Consume local offsets before continuing the preserved upstream pagination token") and a timestamp-group limit caveat, but the phrasing "Local limits apply to timestamp groups" is cryptic and does not clearly state the constraint.

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-loading with "NEA four-day outlook" is good and there is no filler, but the trailing two sentences are dense, jargon-heavy, and harder to parse than they need to be for what they convey.

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 seven optional parameters at 14% schema coverage and no output-schema explanation needed, the description still leaves the area/region/station_id relationship and the actual meaning of the pagination and limit rules unstated. An agent could call it, but not confidently filter by location.

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 14% — only date is documented — so the description carries the burden. It clarifies date default and hints at limit/offset/pagination_token coupling, but says nothing about area, region, or station_id, which are three of the seven parameters, leaving the filtering model unexplained.

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?

"NEA four-day outlook" names a specific resource and time horizon, and the tool name confirms it returns a forecast. It does not, however, distinguish itself from the sibling forecasts singapore_get_forecast_2h and singapore_get_forecast_24h, so the agent must infer the difference from the name alone.

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 only usage-adjacent statement is "latest if omitted" for the date, which describes a default rather than when to choose this tool. There is no mention of when to prefer the 2h/24h forecasts or what the tool is unsuitable for.

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