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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the output (lat/long) but gives no details on network calls, data source behavior, side effects, or the fact that most schema parameters are discarded. It does not mention that inputs like 'ref' and 'url' are ignored, which is surprising given the 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, which is concise and easy to parse. However, it lacks structure: no emphasis on key inputs, no examples, and no logical flow that helps an agent understand how to use the tool. It is brief but not well-organized for usability.

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 9 optional parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain what the output looks like, how the parameters interact, or what happens with discarded values. An agent would have little idea how to correctly invoke this tool, making it essentially unusable without additional investigation.

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 provides descriptions for all 9 parameters (100% coverage), so the baseline is 3. However, the tool description adds no meaning beyond the schema and does not indicate which parameter is the 'place' for which lat/long is returned. The 'city' parameter seems relevant, but the description never references it, leaving the agent uncertain about parameter selection.

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 core function: returning latitude and longitude for a place via Open-Meteo. However, it does not specify which input parameter identifies the place, and the schema contains many unrelated parameters (ref, url, feed, etc.), creating ambiguity. It also fails to distinguish from sibling tools like weather-hint or iana-zones, which also deal with location data.

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. The description provides no conditions, prerequisites, or context that would help an agent decide between geo-hint and other geo-related tools. It is a bare statement with no usage context.

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