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

There are no annotations, so the description carries the full behavioral burden. It only discloses the external dependency on Open-Meteo, but says nothing about side effects, discarded inputs, authentication, rate limits, or what happens when the place cannot be resolved.

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 sentence is brief and free of fluff, but it is under-specified: it reads more like a fragment than a complete tool definition and omits enough context to be properly useful.

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 a seven-parameter schema containing several seemingly unrelated fields (ref, url, feed, host, json, path), no output schema, and no annotations, a single phrase about latitude and longitude is far from enough for an agent to select and invoke 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 already describes all seven parameters, giving high schema coverage. The description adds no parameter-level meaning and does not say that `city` is the relevant input for the latitude/longitude result, so it provides little value beyond the 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 states the tool returns latitude and longitude for a place via Open-Meteo, so the core purpose is recognizable. However, it is a noun phrase rather than an explicit action, does not specify how a 'place' is supplied (e.g., city), and does not distinguish it from nearby sibling tools like weather-hint.

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?

No usage guidance is provided. There is no mention of when to choose geo-hint over weather-hint or other location-related siblings, and no exclusions or alternative tools are named.

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