APIbase

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

With no annotations provided, the description carries the full burden and successfully discloses the data source (Geoapify/OSM) and output structure components. However, it omits operational details like rate limits, error handling for invalid coordinates, or authentication 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?

Single, front-loaded sentence with zero waste. Efficiently combines action, input format, output structure, and data source attribution without unnecessary verbosity.

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?

Despite no output schema and no annotations, the description fully compensates by detailing the expected return structure ('street, city, country, postal code'). For a simple 3-parameter tool, this provides sufficient context for invocation.

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% with clear parameter descriptions already provided in the schema. The description mentions 'lat/lon' reinforcing the coordinate parameters but does not add significant semantic value beyond the schema definitions.

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 specific action ('Convert geographic coordinates') and output ('structured address — street, city, country, postal code'), distinguishing this as reverse geocoding (coordinates→address) versus forward geocoding siblings like geo.address.geocode.

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 by explaining the coordinate-to-address transformation, but lacks explicit guidance on when to choose this provider (Geoapify/OSM) over sibling alternatives like address.geocodio.reverse, or when to use versus geo.ip.geolocation.

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