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

With no annotations, the description must disclose behavior, but it only offers a single sentence. It fails to mention that most parameters are discarded after checks, that the result is a 'hint' rather than definitive coordinates, or that it relies on an external weather API. No behavioral context is given.

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 concise but under-specified and misleading. It is a single sentence that doesn't front-load the essential information; instead, it leads with a claim that doesn't align with the schema. The brevity is not beneficial because it omits necessary details.

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?

Without an output schema and with nine optional parameters, the description is severely incomplete. It doesn't explain the return format, which parameters are needed for a meaningful call, or how the tool behaves with different inputs. An agent cannot correctly invoke this tool based solely on the description.

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 schema has 100% coverage with per-parameter descriptions, but the tool description adds no value in linking these parameters to the stated purpose of returning lat/long. For instance, the schema describes 'ref' and 'json' as discarded inputs, yet the description doesn't clarify which parameter (if any) identifies the 'place' for which coordinates are returned, creating a semantic disconnect.

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 it provides latitude and longitude for a place via Open-Meteo, which is a specific claim, but the input schema contains nine unrelated parameters (ref, url, feed, json, path, etc.) with no clear connection to geolocation. This creates ambiguity about the tool's actual purpose and fails to distinguish it from siblings like weather-hint or timezone.

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 guidance is provided on when to use this tool versus any of its 26 siblings. The description doesn't mention any conditions, exclusions, or alternatives, leaving an agent completely without direction for tool selection.

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