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

The readOnlyHint annotation already tells the agent this is a safe, non-mutating read, lowering the disclosure bar. The description adds the underlying REST endpoint (GET /v1/geocode/search), which is modest extra context, but says nothing about rate limits, API key/auth requirements, or result ordering behavior.

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?

Two compact sentences with the core purpose front-loaded in the first, followed by the API reference. Nothing is redundant or padded; every clause carries information.

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 read-only lookup tool with fully documented parameters, the description covers what the tool does and what it returns ('coordinates and structured address parts'). No output schema exists, so mentioning the return shape is valuable, though pagination and result-count behavior go unmentioned.

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%, so all seven parameters (bias, lang, text, type, limit, filter, format) are fully documented in the schema itself. The description only restates that input is a free-form address or place name, adding no syntax, format, or default details 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?

States a specific verb and resource: turning a free-form address or place name into coordinates and structured address parts, and names the operation as 'forward geocoding'. It is clear in isolation but never explicitly distinguishes itself from close siblings like geoapify_geocode_reverse or geoapify_geocode_autocomplete.

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 term 'forward geocoding' and the direction of transformation (address → coordinates), so an agent can infer the use case. However, it offers no explicit when-to-use guidance, no exclusions, and never names the alternative tools (reverse geocoding, autocomplete) that share its namespace.

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