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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states that it returns coordinates via Open-Meteo, implying an external API call, but does not disclose side effects, idempotency, error behavior, or what happens with invalid input. The schema descriptions mention 'discarded' for several parameters, which hints at internal checks, but these are not explained in the tool description. This is a significant transparency gap for a tool that likely makes network calls.

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, which is concise and front-loaded with the core purpose. However, it is so brief that it omits necessary detail. It is not verbose, but the minimalism comes at the cost of completeness, so it earns a middle score.

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 9 parameters, none required, and no output schema, the description is severely incomplete. It does not explain how to use the tool, which parameter identifies the place, what the expected response format is, or any constraints. The agent is left with no guidance on constructing a valid call. The schema itself is misleading with unrelated parameter descriptions, and the tool description does not resolve this.

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 description coverage is 100%, so each parameter has a description, but these descriptions are unrelated to the tool's stated purpose. For example, 'Git ref name; discarded after the shape check' and 'JSON text to validate; discarded after the check' do not clarify how any of these parameters contribute to returning latitude/longitude. The description adds no meaning beyond the schema and fails to identify which parameter(s) are used to specify the place. It does not compensate for the confusing and seemingly irrelevant parameter set.

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 verb and resource: 'Latitude and longitude for a place via Open-Meteo.' It is specific and unambiguous about the tool's core function. However, it does not differentiate from sibling tools like weather-hint or timezone, which also deal with location-related data, so it loses a point for lack of sibling differentiation.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention any prerequisites, exclusions, or conditions for choosing geo-hint. The schema has 9 parameters but none are required, and the description gives no hint about which parameter to provide to specify a place. This leaves the agent without direction on invocation context.

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