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

With no annotations provided, the description carries the full burden. It does not disclose that the tool makes an external API call to Open-Meteo, what happens when no place is specified, or that many parameters are discarded. The schema hints at discarding but the description omits any behavioral detail, making it opaque.

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, so it is concise and front-loaded with the purpose. However, it is under-specified to the point of being unhelpful, and the lack of structure around parameter usage reduces its effectiveness.

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 9 optional parameters, no required fields, no output schema, and no annotations, the description is woefully inadequate. An agent cannot determine how to call the tool correctly, which parameter yields coordinates, or what the response format looks like.

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?

Although schema coverage is 100%, the parameter descriptions do not connect to the geocoding purpose. For example, 'city' is described as a weather hint, not as the place for coordinates, and parameters like 'ref', 'json', and 'path' appear unrelated. The description adds no meaning to guide an agent on which parameter to use.

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 clear purpose: returning latitude/longitude for a place via Open-Meteo. However, it does not clarify which of the 9 optional parameters identifies the place, and the schema's parameter descriptions (e.g., 'city' as a weather hint, 'ref' as a git ref) do not align with geocoding. This ambiguity weakens the clarity.

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 like weather-hint or timezone, no prerequisites, and no indication of which parameter to supply. The description merely states what it does without any usage context.

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