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

With no annotations provided, the description bears the full burden of behavioral disclosure. It mentions the external service (Open-Meteo) and the output (coordinates) but omits critical details like error handling, rate limits, or how parameters like 'ref', 'url', or 'json' relate to the tool's purpose. The mismatch between the narrow description and the broad, generic schema further reduces transparency.

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 extremely short, which is not inherently bad, but it under-specifies the tool. A single sentence fails to cover the tool's behavior, parameter usage, or output. It is under-specification rather than effective conciseness.

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 9 parameters, no annotations, and no output schema, the description is drastically incomplete. It does not explain how to specify a place, what the return format is, or any constraints. An agent cannot confidently invoke this tool based solely on the provided information.

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 schema coverage is 100%, the parameter descriptions are generic and not tailored to geocoding. For instance, 'city' is described as 'City name for a public weather hint' rather than as a place name for coordinates, and other parameters (ref, url, feed, host, json, path, zone, query) appear unrelated. The tool description does not clarify which parameter carries the place input, so the schema adds little meaningful semantic guidance.

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 a clear action and resource: obtaining latitude and longitude for a place via Open-Meteo. It is concise and informative, though it does not differentiate from sibling tools like weather-hint or timezone, which could also involve location data.

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 gives no guidance on when to use this tool versus alternatives. It does not mention specific scenarios, prerequisites, or exclusions, leaving the agent to infer usage solely from the name and schema.

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