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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context whatsoever: nothing about rate limits, whether results are ranked, coverage of the underlying geocoder, or how the q-vs-structured-field mutual exclusion behaves in practice.

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?

It is certainly short and front-loaded with no filler, but at three words it is under-specified rather than genuinely concise. Brevity here costs the agent information rather than saving it effort.

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?

A 13-parameter geocoding tool with an output schema and read-only annotations needs only a modest description, but this fragment does not even establish the input/output contract or route the agent away from geocoding_lookup and geocoding_reverse. The structured fields carry the rest, but the definition as a whole feels incomplete.

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% across all 13 parameters, including the q-vs-structured-field exclusivity rule and defaults for limit, extratags, namedetails, addressdetails. With the schema doing all the work, the baseline of 3 applies; the description contributes nothing additional.

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 phrase 'forward search' plus the tool name geocoding_search conveys the address-to-coordinate direction and implicitly contrasts with the geocoding_reverse sibling. However, it is a three-word fragment that never states what a result is (coordinates, normalized address, place IDs) or what input form is expected, so the agent gets only the vaguest sense of purpose.

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 explicit when-to-use guidance and no mention of geocoding_lookup or geocoding_reverse as alternatives. The word 'forward' is the only implicit signal that this is not the reverse-geocoding tool, which is thin but not nothing.

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