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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only says Open-Meteo is involved; it does not mention that the call is external, that most schema inputs are discarded, whether anything is persisted, or failure behavior. The schema's 'discarded after...' notes are not reflected in the description.

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, front-loaded sentence with no filler, which is positive. But it is under-specified rather than appropriately sized: for a tool with a seven-property schema and no annotations, this level of brevity omits essential selection and invocation details.

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 confusing multi-property input schema and the absence of annotations, the description is not complete enough to call correctly. It does not specify which parameter to supply, whether that parameter is required, what the output shape is, or how failures are reported. An agent would be guessing between city, url, host, and path.

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 adds no mapping to parameters. Although the schema has per-property descriptions, the only plausible geo-related property is city, and its description says it is for a 'public weather hint' and is discarded—this reads like weather context rather than a geocoding input. The other properties (ref, url, feed, host, json, path) are not explained in relation to returning 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 names a concrete deliverable—latitude and longitude for a place—and identifies the provider, Open-Meteo, which distinguishes it from a weather lookup. However, it is phrased as a noun fragment rather than an explicit 'uses X to return Y' statement, and the schema's many unrelated properties (ref, feed, json, path) leave ambiguity about what counts as a 'place'.

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 about when to call geo-hint versus siblings like weather-hint, domain-shape, or lib-docs-hint. The description mentions only the provider, giving no decision criteria, prerequisites, or exclusions.

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