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

With no annotations, the description carries full burden, but it only says coordinates are provided. It does not disclose read-only behavior, error handling, output format, or what happens with discarded parameters.

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 short sentence, which is concise, but it omits essential details and is not front-loaded with actionable information. The oversized schema contradicts the brevity and makes the tool appear unfocused.

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?

There is no output schema, no example, no mention of return values or failure modes, and no explanation of how to provide the place name. The description is completely inadequate for an agent to reliably select and invoke this tool.

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 parameters are almost entirely unrelated to geographic coordinates, and descriptions like 'City name for a public weather hint' are misleading. There is no indication which parameter, if any, is actually used to fetch latitude and longitude.

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 returns latitude and longitude for a place via Open-Meteo, but it lacks a clear verb and does not specify which of the nine parameters identifies the place. The title 'geo-hint' is not enough to disambiguate from sibling tools like 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?

No guidance is given for when to use this tool versus alternatives such as weather-hint or lib-docs-hint. The description does not mention prerequisites, input requirements, or any situational context.

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