os_net_station_get

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, which cover the safety and side-effect profile. The description adds the 'metadata' qualifier, which clarifies the nature of the resource beyond the tool name. This is sufficient given the annotation coverage, though it doesn't elaborate on response structure (covered by output schema).

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, front-loaded with the action and resource, and contains zero fluff. It efficiently conveys the core purpose without unnecessary detail.

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?

The tool is simple with one required parameter and an output schema, so the description covers the essential purpose and parameter. It doesn't mention how to obtain a stationId, but that's likely covered elsewhere. Given the low complexity and existing annotations and output schema, the description is adequate.

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?

With 0% schema description coverage, the description must compensate for parameter meaning. It mentions 'by stationId', which clarifies the role of the parameter as the identifier, but it doesn't explain what stationId is, its format, or where it comes from. This is minimal but adds some value over the schema, which only lists it as a string.

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 states a specific verb (Get), a clear resource (OS Net station metadata), and the lookup key (stationId). It distinguishes from siblings like os_net_station_log (logs) and os_net_rinex_years (RINEX data) by specifying metadata, so an agent can tell them apart.

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 makes it clear that this tool is for retrieving metadata by a station identifier. It doesn't explicitly name alternatives or exclusions, but the context is clear and no competing tool is implied. The lack of explicit when-not-to-use guidance is a minor gap, keeping it below a 5.

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