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

With no annotations, the description carries the full burden of explaining behavior, but it does not disclose that most schema parameters appear unrelated or are described as 'discarded'. It also does not clarify what happens with multiple inputs, whether a place lookup is required, or what output format is returned beyond 'latitude and longitude'.

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 that is easy to parse and front-loads the key information. It earns a high score for conciseness, though it omits important usage details that would make it fully self-contained.

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 tool has nine optional parameters, no output schema, and no annotations, the description is far too thin to be complete. It does not specify which parameter identifies the place, what the coordinate format is, or how errors or invalid inputs are handled.

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?

Although every parameter has a schema description, those descriptions seem mismatched with the geo-hint purpose (e.g., Git refs, RSS feeds, JSON validation, file paths). The description does not clarify which parameter is actually used for the place lookup, and all parameters are optional, leaving the agent uncertain about what to provide.

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 clearly states that the tool returns latitude and longitude for a place via Open-Meteo, which identifies the core purpose and distinguishes it from most sibling tools. It lacks an explicit verb like 'get' or 'return', but the meaning is still 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?

The description provides no guidance on when to use this tool instead of the many similar sibling tools, nor does it explain which input parameter should be supplied to identify the place. There is no mention of alternatives, prerequisites, or selection criteria.

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