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

No annotations are provided that clarify side effects, read-only behavior, or error conditions. The schema descriptions mention 'discarded after the shape check' and similar phrases, but the description does not disclose that many parameters are ignored or that the tool may have multiple modes.

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, but it lacks structured information (e.g., input, output, usage). Given the complexity of the schema (nine parameters), this is under-specified rather than concisely complete.

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?

The description fails to specify what the tool returns, which parameters are valid, or how to formulate a request. It is a minimal fragment that leaves almost all necessary context unaddressed.

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 does not explain which of the nine parameters are actually used or how they relate to retrieving latitude and longitude. It adds no value beyond the already-ambiguous schema parameter descriptions.

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 is a noun phrase ('Latitude and longitude for a place via Open-Meteo.') rather than a clear verb statement like 'Returns latitude and longitude for a location.' It hints at the resource and method but does not explicitly state the action the tool performs.

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 provides no guidance on when to use this tool versus any of the many siblings (e.g., weather-hint, timezone, normalize-url). No alternatives or distinguishing criteria are mentioned.

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