get_station_info

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns metadata (name, ID, location, elevation) and is specific to one station, but does not mention any side effects, data freshness, or access requirements. Since there are no annotations to contradict, a 3 is appropriate for a read-only metadata tool.

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 sentence with no wasted words, clearly stating the action and listing the returned fields. It is front-loaded and efficiently communicates the tool's purpose.

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 tool has zero parameters, no output schema, and no annotations, the description covers the essential information: what it does, which station, and what data it returns. It could optionally mention if the data is static or dynamic, but the current description is sufficient for an agent to use the tool correctly.

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 no parameters and schema description coverage is 100%, so the description need not add parameter info. The description's mention of the specific station and the fields returned provides useful context beyond the empty schema.

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 specifies the verb 'Get' and the resource 'metadata for the KCALAKEF92 weather station', listing exactly which fields are returned (name, ID, neighborhood, country, GPS coordinates, elevation). It distinguishes from siblings like get_current_conditions and get_daily_summary which focus on weather data rather than station metadata.

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 explicitly names the station (KCALAKEF92) and states it returns metadata, implying it's for station information rather than weather data. However, it doesn't explicitly say when not to use it or compare to siblings, though the station-specific nature and listed fields make the context clear.

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