singapore_list_weather_stations

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 a completeness claim ('No observations omitted from a claimed national inventory'), which is opaque and arguably misleading since this tool lists stations, not observations, and it says nothing about pagination behavior for a paginated endpoint.

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?

Two compact clauses, front-loaded with the core capability and result shape. The trailing inventory sentence is cryptic and costs more than it earns, keeping it from a 5.

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?

An output schema exists, so return values need no prose, and annotations cover safety. However, for a paginated discovery tool with zero schema coverage, the missing limit/offset guidance and unclear inventory claim leave real gaps for correct invocation.

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 must carry parameter meaning; it clarifies two of four params — 'measure' for routing and 'query' for ID/name search. It says nothing about 'limit' (max 100) or 'offset', including the default page size, leaving pagination semantics 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 ('Discover weather stations'), plus what it returns (IDs, WGS84 coordinates) and the two discovery modes ('by observed measure' or 'search by ID/name'). It does not explicitly position itself against the many sibling get_* / query_* weather tools, so it falls short of a 5.

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?

Usage is implied rather than stated: an agent can infer it should call this to obtain station IDs before querying observations, but the description never says when-not to use it or which sibling (e.g. singapore_get_air_temperature) it complements. Adequate but leaves routing to inference.

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