geocode_address

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that multiple matches may be returned ('List of matching locations') and what each result contains, but says nothing about no-match behavior, ambiguity/disambiguation, rate limits, or any auth requirements.

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 first sentence is a strong front-loaded summary, but the second paragraph largely restates it and the Returns block duplicates a field-by-field list that the output schema already provides.

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 single-parameter lookup tool with an output schema covering the return shape, the description supplies adequate input semantics and result content. Missing only edge-case behavior (no results, ambiguous queries) and any operational constraints.

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 0%, but with only one parameter the description compensates well by enumerating accepted input forms with concrete examples (landmark names, street addresses, parks), which is meaning the bare 'address: string' schema does not convey.

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?

States a specific verb+resource (convert an address to geographic coordinates) and the input domain is unambiguous. The address-to-coordinates direction implicitly distinguishes it from reverse_geocode, but no sibling is named explicitly.

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?

Usage is implied by the input/output direction and the closing note that results feed 'other geospatial tools,' but there is no explicit when-to-use vs. when-not guidance and no named alternative such as reverse_geocode for the opposite direction.

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