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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the bar is lower. The description adds the underlying REST endpoint, but says nothing about authentication, rate limits, quota behavior, or how ambiguous matches are ranked — context that would help an agent decide whether one call suffices.

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 short sentences, the capability statement front-loaded ahead of the endpoint detail, with no filler. The REST endpoint line is arguably noise for an agent that never needs the raw path, but it costs only one clause.

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?

Complete for a single-required-parameter, read-only lookup whose annotations carry the safety profile and whose schema carries all parameter semantics. The phrase 'coordinates and structured address parts' tells the agent what comes back, which is sufficient absent an output schema.

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 every parameter (bias, lang, text, type, limit, filter, format) is already documented with an example in the schema. The description adds no syntax, default, or interaction detail beyond that, which is the baseline-3 case when the schema does the work.

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 ('turn a free-form address or place name into coordinates and structured address parts') and adds an implementation anchor (GET /v1/geocode/search). The word 'Forward' implicitly distinguishes it from the reverse-geocoding sibling, but nothing explicitly separates it from 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 only implied: 'free-form address or place name' suggests complete input rather than the partial-input case that autocomplete handles. No explicit when-to-use statement, no exclusions, and the sibling tools that compete for the same request (autocomplete, place_details) are never named.

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