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

With no annotations, this sentence carries the full transparency burden, but it only names the external provider. It does not mention that Open-Meteo is called over the network, how failures or rate limits behave, or that every parameter except the place input is discarded after a shape check.

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 single sentence is compact and front-loaded with the core function, avoiding filler. But it is so terse that it omits essential routing and input information, making under-specification the limiting factor rather than prose quality.

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?

For a tool with nine optional parameters, no output schema, and no annotations, this description is incomplete. It does not clarify which parameter to provide, what the returned coordinates look like, or what safety or network expectations exist, so an agent cannot invoke it reliably from the description alone.

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 all parameters have schema descriptions, the tool description does not map 'place' to the `city` parameter or explain how `url`, `ref`, `path`, `zone`, `query`, or `json` relate to a geographic lookup. The `city` schema description even references a weather hint, not geocoding, so the agent cannot confidently select the right input.

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 phrase 'Latitude and longitude for a place' communicates a geocoding result and identifies Open-Meteo as the source, so it is more than a tautology. However, it never states which of the nine schema parameters supplies the place, leaving a clear gap between purpose and invocation.

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?

The description offers no guidance on when to use geo-hint instead of closely related siblings such as weather-hint, timezone, or normalize-url. There are no conditions, exclusions, or alternative tool names, so an agent must guess when this tool is appropriate.

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