geocode

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

No annotations are provided, so the description carries full burden. It discloses the underlying geocoder (Esri World), the output structure (matched address, lat, lon, match score, and a summary), and gives an example. It does not mention error handling or edge cases, but for a read-only lookup tool, this is adequate transparency.

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 concise and well-structured: a one-sentence purpose, followed by Args and Returns sections. Every sentence serves a purpose, and the main functionality is front-loaded.

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 is a simple one-parameter geocoder with no annotations or output schema, the description is complete: it explains what the tool does, the input format, and the return structure. No additional information is needed for an agent to select and invoke it correctly.

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 provides only a title for the single 'address' parameter (0% description coverage). The description compensates fully with an 'Args' section explaining it is a free-form address string and provides a concrete example ('2437 Remount Rd, Charlotte, NC'), adding meaningful value beyond the schema.

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 tool geocodes a free-form address to lat/lon using the Esri World geocoder, specifying both the action and the resource. This distinguishes it from sibling tools which are all data lookups (e.g., lookup_parcel, crime_near) rather than address-to-coordinate conversion.

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 implies usage through its purpose statement ('Geocode a free-form address to lat/lon'), and the example shows a typical input. However, it does not explicitly state when to prefer this over alternatives or provide any exclusions, so guidance is only implied.

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