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

With no annotations, the description carries the transparency burden. It does disclose the external data source (Nominatim) and the core behavior (place/address to lat/lon), but it does not mention potential rate limits, external network dependency, failure behavior, or required attribution, leaving some behavioral context implicit.

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 short and front-loaded, with the core purpose stated immediately. It loses a point for the redundant 'Geocode:' prefix that largely repeats both the tool name and the opening verb, but overall it contains minimal waste.

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 simple tool with no output schema and no annotations, the description covers the essential input (query or address) and output (latitude and longitude). However, it omits the purpose of the 'input' parameter, gives no guidance on how results are structured, and does not address what happens when geocoding fails, leaving the agent to guess.

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 schema descriptions are tautological ('Input to process', 'Query to process', 'Address to process'), so the tool description must add meaning. It clarifies that query or address can be provided and that the result is coordinates, but it leaves the 'input' parameter completely unexplained and does not say whether the parameters are mutually exclusive or aliases.

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 the verb (geocode), the resource (place name/address), and the outcome (coordinates via OpenStreetMap Nominatim). It effectively describes forward geocoding, which distinguishes it from reverse-geocode and address validation tools, though it does not explicitly name or contrast any sibling.

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?

It tells the agent to provide a query or address, which is a useful invocation hint. However, it gives no explicit guidance on when to prefer this tool over alternatives like reverse-geocode or ip-geo, and no conditions or exclusions.

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