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

With no annotations, the description carries the full behavioral burden, yet it only names the external provider. It does not disclose that this is a network-backed lookup, what happens on failure, whether any state is retained, or what exact payload is returned.

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 nine-word phrase with no filler; it front-loads the output and the provider. It earns its place despite being terse.

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 no annotations and no output schema, this is incomplete: an agent does not know which parameter to pass, what the returned coordinates look like, or what error conditions exist. The presence of eight other optional parameters makes this ambiguity worse.

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?

Schema coverage is 100%, so the baseline is 3 despite the description containing no parameter details. The description does not map 'place' to the city parameter, and the schema's unrelated optional fields (ref, json, feed, etc.) could confuse selection, but the city property is present and documented.

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 identifies a concrete outcome — latitude and longitude for a place — and names the data source (Open-Meteo). It lacks an explicit verb and does not contrast with sibling tools, but the intent is reasonably unambiguous.

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 when-to-use or when-not-to-use guidance is provided, and no alternatives are named. 'For a place via Open-Meteo' weakly implies geocoding, but does not explain when this tool should be selected over weather-hint or other lookup tools.

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