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

With no annotations, the description must carry the full behavioral burden. It mentions an external service (Open-Meteo) but does not disclose that the tool may perform multiple unrelated checks (as implied by parameter descriptions like 'discarded after the shape check') or that it makes network calls. The description's narrow claim about lat/long conflicts with the broad parameter set, making actual behavior opaque.

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 sentence and technically concise, but it is so underspecified that it misleads. Conciseness without content is not a virtue; the sentence omits all operational detail and does not front-load the key usage information. The structure offers no benefit.

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 parameters, no output schema, and no annotations, the description is severely incomplete. It does not specify which parameter identifies the place, what the output format is, whether it is synchronous, or any side effects. The tool's complexity demands far more explanation than a single high-level sentence.

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?

While schema coverage is 100% and each parameter has a description, the tool description adds no value in mapping parameters to the stated purpose. The schema descriptions themselves are more informative about behavior (e.g., 'discarded after the shape check') but do not align with the 'place' concept, so the agent cannot infer which parameter to use for geocoding. The description fails to synthesize the schema into a usable mental model.

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 specific outcome (latitude/longitude for a place via Open-Meteo) but fails to explain how the place is specified, especially given the nine parameters that include ref, url, feed, host, json, path, zone, and query—none of which clearly map to a place name. It also does not differentiate from sibling tools like weather-hint or timezone, which likely also involve place or coordinate 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?

No guidance is provided on when to use this tool versus alternatives, nor which parameter to supply for the 'place' input. The description is silent on context, prerequisites, or exclusions, leaving the agent without any basis to choose this tool over its siblings.

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