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

With no annotations provided, the description carries the full burden. It reveals the basic output (coordinates) and external service (Open-Meteo), but omits behavior around parameter handling, side effects, failures, and output format.

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 brief and free of fluff, but it is a noun phrase rather than a complete sentence and is too sparse to be considered well-structured for a tool with nine parameters.

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 complex schema with nine optional parameters and no output schema, the description is far from complete. It lacks parameter mapping, usage examples, output details, and error behavior.

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 every parameter has a schema description, many descriptions are confusing or unrelated to geocoding (e.g., 'Git ref name; discarded after the shape check', 'JSON text to validate; discarded after the check'). The tool description does not explain how any of the nine optional parameters maps to a place lookup.

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 that the tool returns latitude and longitude for a place via Open-Meteo, but it lacks an explicit verb and does not explicitly distinguish it from sibling tools such as weather-hint.

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, no mention of expected inputs, and no context about which parameter represents the 'place'.

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