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 only mentions lat/long, but the schema parameters describe a variety of shape checks (e.g., 'discarded after the shape check'), implying the tool is a generic validator. This is misleading—an agent would expect only geocoding behavior and would not know the tool also handles URL, JSON, file paths, etc. The description fails to disclose the true scope.

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 concise sentence, which is efficient. However, given the tool's 9-parameter complexity, this brevity leads to under-specification. The structure does not front-load important context or separate the primary geocoding function from the other shape-check capabilities implied by the schema.

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?

The tool has 9 parameters, no annotations, and no output schema, so the description is the sole source of contextual information. It covers only one narrow function and omits the tool's other apparent behaviors, return format, error conditions, and any usage constraints. This is severely incomplete for an agent to call the tool correctly across its possible uses.

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 description does not clarify which parameter is used for the lat/long functionality (presumably 'city', but not stated). While the schema has 100% coverage with individual parameter descriptions, the tool description adds no value in explaining how parameters relate to the stated purpose. The mismatch between the description and schema further confuses parameter meaning.

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 'Latitude and longitude for a place via Open-Meteo,' which is a specific and clear function, but the schema includes 9 unrelated parameters (ref, url, feed, host, json, path, zone, query) that suggest the tool does much more than geocoding. This makes the stated purpose incomplete and potentially misleading, and it does not differentiate from siblings like weather-hint beyond the obvious lat/long distinction.

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 context for when geocoding is needed, nor any exclusions or conditions. An agent cannot infer when this tool is appropriate compared to siblings like weather-hint or timezone.

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