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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that the tool returns mountpoint, host, distance in km, and baseline grade, and mentions the data source (KUON GEO's 10-minute polling). It doesn't disclose limitations like result count, accuracy, or error behavior, but the read-only nature is implicit. This is adequate but not rich.

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, front-loaded sentence that states the core function immediately. It packs useful details (worldwide, NTRIP, data source, return fields) without unnecessary words. Minor deduction for dense phrasing that could be slightly clearer on parameter meaning.

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?

For a simple two-parameter tool with no output schema, the description covers the main purpose and output fields. However, it omits practical details like result ordering, maximum number of bases, or any constraints (e.g., distance limits). Given the tool's simplicity, this is a moderate gap, not a critical one.

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 explain lat and lon. It only implies they represent a point ('to a point') but doesn't specify coordinate format, units, or required ranges. This is a significant gap for a tool with only two parameters, leaving the agent to guess at standard lat/lon conventions.

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 states the tool finds the nearest online community RTK base stations (NTRIP) to a point, worldwide. It specifies the resource and the operation ('nearest'), which is unambiguous. While it doesn't explicitly differentiate from siblings like gnss_in_japan, the domain is distinct enough that an agent can infer its purpose without confusion.

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?

There is no guidance on when to use this tool versus alternatives. No exclusions, prerequisites, or conditions are mentioned. The description implies use when you need nearby RTK bases, but it doesn't address other contexts or mention sibling tools that might be more appropriate for different queries.

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